Loading ToolBench
The privacy guide, the 64-vertex sovereignty lattice and the City Key as MCP tools — the Mage's read tools of the Verifiable Trust Agent. Zero dependencies.
17 tools with complete JSON schemas and descriptions. Naming follows verb_noun pattern (experience_overview, city_invitation_draft, journey_start, etc.). Descriptions are detailed (100-300 chars) and explain WHAT the tool does and WHEN to use it. However, parameter descriptions are sparse or missing entirely, most params lack guidance on format, constraints, or expected values. Output schemas are not documented. Error handling is implicit (no recovery guidance in descriptions). All tools are READ_ONLY, reducing risk but also limiting composition patterns.
Prepare a short-lived spell/sticker proposal for explicit extension review. Does not connect to a browser, authorize, cast, place, issue credentials or earn mana. Reuse operationId for the same logical action. Do not include secrets in page URLs or target IDs.
Prepare a PRIVATE draft of a City Portal invitation, offer, request or visitor mark. publish stays false; this does not sign, send, admit, issue a credential or create a MyTerms agreement. Supply only a summary the keeper may choose to make public.
Start here: source capability inventory for City invitation, Star/key custody, learning, browser actions, agreements and scoped access. Distinguishes implemented local tools from pending live services and design proposals. Not live discovery or authorization.
Find existing site entry points and MCP tool sequences for arrival, learning, key custody, casting and collaboration. Static guidance only; it does not discover live services or transmit your key.
Linked pages (outgoing and backlinks) of a page, each with the NAMED LATTICE MOVE from this page to it: succ · neg · bnot · flip <dimension> · jump ×k (dimensions), per the 64-vertex sovereignty lattice.
Parameter descriptions missing or minimal. Most params (e.g., 'key', 'bundle', 'packet', 'vertex', 'op') lack guidance on format, constraints, or expected values. LLMs cannot infer meaning from names alone.
Output schemas not documented. Tools return complex objects (evolved keys, journey bundles, lattice vertices) but no schema describes the response structure. Agents cannot plan downstream calls or extract fields reliably.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | 2025-06-18+ | v2 |
One page by slug (site optional — identity is the slug, never the host): its text, weave (links), lattice vertex + six-bit posture, PSI element and public URL.
Search the guide (the baked fedwiki federation, 20 sites). Returns an ORDERED WALK of pages — BM25 over the baked lexical index, then link-graph expansion — each step with its site, slug, lattice vertex and PSI element. The agent reads the bake, never the live farm, so a walk is reproducible.
Project a Star Hold under optional key constraints: returns the recipient view (linkable, not permission). Filters items by profile and role, computes the projection root, and signs it with the bearer's key if available.
Verify a Star Hold (a signed collection of relationships). Checks the root Merkle hash, every item's signature and profile, the bearer's signature, and optional key match. Returns the verdict, the item states, and an optional projection (recipient view) if responseMode='projection'.
Fold one original artefact packet OR observed Trust Task document into the City Key journey. Returns the private bundle and evolved key with κ/prior. Exact retry is a no-op. Recorded tasks are NOT verified credentials; send only material the holder chose to disclose to this agent.
Read the City journey evidence inventory: integrity, bearer claims, optional signed key record, and pending checks. Never authorizes issuance. Does not verify Trust Task proofs, freshness or comprehension.
Create a PRIVATE journey bundle from a City Key and its complete original packets. Preserves evidence outside the key; no network, signing or credential issuance.
Law L5 — a κ is never trusted, only re-derived. Parse a City Key from JSON, a sigil PNG (base64 or file path), or a data: URL. Verify its κ, extract the walk and its PSI elements, and return the key's identity, carrier type, and integrity verdict.
Evolve a City Key by walking a path through the guide (or a custom walk of vertices). Returns the evolved key with its new κ, prior κ, the walk's PSI elements, and the lattice moves. Deterministic: the same walk always produces the same κ.
Verify a signed VTA record (agentprivacy.vta/1) over a City Key. Checks the Ed25519 signature, the key's κ match, the record's freshness (evolved_since), and optional liveness (horizonDays). Returns the verdict, the key's identity, and the DID.
Apply a lattice operator to a vertex (0-63): succ (the wheel, +1 mod 64), neg (Swordsman reflection, 64−x), bnot (Mage antipode, 63−x), "flip <dimension>" (one bit), or "to <vertex>" (names the move). Returns the resulting vertex, its six bits (d1 protection … d6 value), dimensions, stratum, and a derived reading.
Render a City Key as a sigil (a visual proof carrier): a PNG with the key embedded in a text chunk. The sigil is a short-lived, bearer-only proof of the key's identity and walk. Carries the full key; no secrets are withheld.
No error handling guidance. Descriptions do not explain what errors can occur, how to recover, or what the LLM should do next. E.g., 'key_derive' can fail if the key is malformed, but no recovery path is documented.
Complex parameter types (anyOf with object + string) lack clear guidance. 'key' param accepts JSON object, string, base64 PNG, or file path, but no description explains which format to use when or how the tool disambiguates them.
No composition guidance. Tools operate on City Keys and journey bundles, but descriptions do not explain the typical call sequence (e.g., journey_start → journey_fold → journey_inspect). Agents must infer the workflow.