Read durable memory (notepad-read, 2c). Restore state saved in a previous session.
Sibling: vc_notepad_save, vc_notepad_list.
| Name | Required | Description | Default |
|---|---|---|---|
| note_key | Yes | Note key to read. | |
| owner_key | Yes | Your stable agent identity. | |
| payment_signature | No | Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds durable-memory context and the state-restoration intent, but does not disclose additional behavioral details such as missing-key handling or persistence semantics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded, with the core action in the first sentence. The '2c' fragment is cryptic but not harmful; overall the description wastes no words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only, idempotent tool with a full input schema and an output schema, the description covers the essential purpose and use case. It names siblings for navigation, though it could add a bit more on when reading is preferable to listing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so note_key, owner_key, and payment_signature are already explained in the schema. The description adds no extra parameter-level meaning; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource ('Read durable memory') and adds a concrete use case ('Restore state saved in a previous session'). It also names the sibling tools, which helps an agent distinguish it from vc_notepad_save and vc_notepad_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'Restore state saved in a previous session' phrase gives clear context for when this tool is appropriate. Sibling tools are listed, though the description does not explicitly state when to prefer one over the other.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target a clearly distinct resource and action: notepad save/read/list/share/browse is cleanly separated from workspace create/read/write/list, and pairs like vc_web_search vs vc_page_markdown have explicit boundaries. The four guard tools (state, drift, idempotency, retry storm) share the same advisory-preflight pattern and could be confused at a glance, though their differing nouns and sibling cross-references reduce misselection.
The vc_<domain>_<action> convention with the action verb last is consistent across most tools (v_c_notepad_save, v_c_workspace_create, v_c_square_post, v_c_drift_guard, v_c_attest_verify). Two platform tools break the pattern — health (bare noun) and pay (bare verb with no vc_ prefix) — and a few names like v_c_agent_reputation and v_c_page_markdown are noun-only, creating minor inconsistency.
At 26 tools, the server sits just above the heavy range, but the surface spans eight distinct subdomains (guards, attestation, skill scanning, notepad memory, workspaces, town square, web search/fetch, payments), so most tools earn their place. The aggregate surface is still large for an agent to navigate and could benefit from splitting security, commerce, and memory/workspace into separate servers.
Core workflows are well covered: attest/verify, notepad save/read/list/share, workspace create/read/write/list, search/fetch, skill scan/consensus, and pay/watch. Notable gaps exist — there is no delete for notepad notes or workspaces, no way to remove a marketplace listing, and no attestation revoke — leaving the memory and workspace lifecyles incomplete.