BlackOps Center

Get Note

get_note

Read-only

Get a single note by UUID, slug, or title. Use this to read the full content of individual notes, including brain source notes referenced in a brain manifest. VAULT SYNC STATUS: the response carries a sync block — status is "queued" (commit in flight), "synced" (landed; see file_path + commit_sha), "failed" (see last_error; the sweeper retries), or "none" (no vault target). This is how you confirm a deferred post_notes commit landed; post_notes itself can only report "queued".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_note"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Note UUID, slug, or title

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint annotation, the description discloses the shape and meaning of the vault sync block returned by the tool, with all four status values defined ('queued', 'synced', 'failed', 'none') and the retry behavior explained. That is substantial behavioral context an agent could not infer from the annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and usage guidance are front-loaded in the first two sentences, followed by a clearly labeled 'VAULT SYNC STATUS' block. The status block is dense but every element — each status value plus the retry note — earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description covers the important part of the response by explaining the sync block and its statuses. It does not cover error behavior, such as what happens when no note matches the supplied identifier, which is a modest remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the sole parameter already documents that it accepts a UUID, slug, or title. The description restates those accepted forms but adds no additional disambiguation, such as what happens when a title matches multiple notes or how ambiguous identifiers are resolved.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Get a single note') and enumerates the three identifier forms (UUID, slug, title). It also scopes the use case ('read the full content of individual notes, including brain source notes referenced in a brain manifest'), which separates it from listing tools like get_recent_notes and write tools like post_notes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when to call this tool — reading a full individual note, including brain source notes from a manifest — and explicitly ties the sync block to verifying a deferred post_notes commit, noting that post_notes can only report 'queued'. It stops short of naming alternatives to use instead when the caller is searching or listing notes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BlackOps Center tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?