Skip to main content
Glama
CantorFi MCP server

CantorFi MCP server

Official
by cantorfi

Fetch a CantorFi vault or guide

fetch
Read-onlyIdempotent

Retrieve a complete CantorFi vault record or protocol guide by ID from search results, giving AI agents full details beyond summary listings.

Instructions

Full record of one CantorFi vault or full text of one guide, by id (from search).

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": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered without the description. The description adds that the response is a 'full record' / 'full text' rather than a summary, which is meaningful payload context, but it says nothing about errors for unknown ids, size limits, or object-type resolution.

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

Conciseness5/5

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

A single well-formed sentence with zero filler, and the resource and lookup key are front-loaded. Nothing unnecessary is included.

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?

There is no output schema, so the description usefully signals that the return is a full record or full text rather than a summary. Combined with annotations that cover safety and idempotency, the definition is close to sufficient; the remaining gap is how vault-vs-guide resolution works with only an id.

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 description coverage is 0%, so the description must carry the semantics of 'id'; it does explain the provenance of the id (from search), which is the most important thing an agent needs. It does not describe the id format or how the same id namespace maps to two different entity types.

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

Purpose4/5

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

States a specific verb and resource: returns the full record of one CantorFi vault or the full text of one guide, keyed by id. It distinguishes itself from 'search' by noting the id comes from search. The only ambiguity is that a single 'id' parameter must implicitly determine whether a vault or a guide is returned, which the description does not explain.

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

Usage Guidelines3/5

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

The parenthetical '(from search)' establishes the prerequisite that ids are obtained via the search tool, which is genuinely useful sequencing guidance. However, it gives no when-not guidance and does not differentiate this from the sibling 'cantorfi_vault' tool, so the agent must infer which fetch path to take.

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