GraphSheets

What LocalMark checked

• Published Agent Card

  Inspect the source card ↗. The last successful fetch was 14 Nov 2026, 11:15 UTC.

• Latest card check: passed

  14 Nov 2026, 11:15 UTC · Agent Card validated

• Advertised endpoint: TLS connection passed

  14 Nov 2026, 11:15 UTC · Valid TLS connection to advertised endpoint host; no A2A request sent This does not test the A2A protocol or run a task.

• Read-only protocol probe: Authentication required

  14 Nov 2026, 05:14 UTC · Endpoint requires authentication; A2A response not confirmed LocalMark sent no message and did not request task creation.

• Unsigned card

  This card does not provide a digital signature. Checked 14 Nov 2026, 11:15 UTC.

• 30-day card check history

  2 of 2 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.

• Publisher claim

  No publisher claim has been completed for this listing.

Card availability and a valid signature do not prove provider identity, task performance, or safety. Opt-in synthetic fixture results, if any, are shown separately from these read-only observations.

Recent card checks

Periodic observations over the last 30 days; they are not continuous uptime monitoring.

View the 30-day check log as JSON →

Declared skills 6

• Explain a figure

  Why a value is what it is: the evaluation trace behind one node in one period — its formula, each input's value and whether it came from a formula, an input, an actual override or an error. `depth` follows the trail further. Send a data part {"skill": "explain-figure", "arguments": {…}}; the arguments are the `explain` tool's.

  explainaudittrace
• List models

  The models this token can see: uid, title, head hash, when last changed, and the verification rung each is on. Send a data part {"skill": "list-models", "arguments": {…}}; the arguments are the `model_list` tool's.

  modelslist
• Model overview

  The model at a glance: title, axis, scenarios, sections with node counts, ledgers, whether uncertainty is declared, the verification rung, check status per scenario and lint counts. Call this first. Send a data part {"skill": "model-overview", "arguments": {…}}; the arguments are the `model_overview` tool's.

  modelsoverview
• Read values

  Evaluated values for named nodes across the axis in a scenario, actuals overriding where present. Errors appear as their code (#REF, #DIV/0). A node whose title carries references (`{{fiscal.royalty_threshold}}`) has it worked out in that scenario under `titles`, as the reader sees it. Ask for the nodes you need, not the model. Send a data part {"skill": "read-values", "arguments": {…}}; the arguments are the `values_get` tool's.

  valuesfiguresforecast
• Search a model

  Find nodes by a word in their name, title, description, source, unit or formula, optionally restricted to a kind (input, calculated, constant, check, ledger). Returns declarations, not values. A kind with no query lists every node of that kind. Send a data part {"skill": "search-model", "arguments": {…}}; the arguments are the `model_search` tool's.

  modelssearch
• Verify a model

  Run the verification ladder on the model as it stands: validation issues, every lint finding with its rule and node, every check per scenario with its failing periods, the rung, and `connectivity` — the inputs nothing reads, the inputs with no values, the calculated rows nothing reads or shows, the ledger columns no formula reads, and the rows of reported history nothing reads — which is whether the graph runs from inputs through formulas to outputs. `severalRates` lists any IRR whose cashflows have more than one rate, with every rate and the one the row shows. A row named as the model's answer, one `risk_set` reports, one a statistic asks about and one a scoped check covers are all read or shown, so none of them is listed. The authoritative answer to 'what is wrong'. Send a data part {"skill": "verify-model", "arguments": {…}}; the arguments are the `verify` tool's.

  checkslintverify