Annalist Financial Statements

Fetch a document

fetch

Read-onlyIdempotent

The full text of one document that search returned (an overview, key findings, a statement or the ratios of one frequency of a company), as JSON with its figures, units, periods and source document ids, with the address of its page for the citation.

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

Name	Required	Description	Default
`id`	Yes	a document id from search, for example company:apple or statement:apple:pl_annual

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world fetch, so the safety profile is covered. The description adds useful behavioral context about the returned payload, including figures, units, periods, source document ids, and the page address for citation, though it does not discuss missing documents or error behavior.

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 description is a single front-loaded sentence with no filler. It is somewhat dense and includes return-content details that may duplicate the output schema, but it remains efficient and readable.

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 simple one-parameter read-only fetch tool with an output schema, the description provides enough context to call it correctly: source of the id, content type, and citation behavior. The main gap is that it does not explain its relationship to the specialized sibling retrieval tools.

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 schema already documents the single `id` parameter as a document id from search with examples. The description reinforces that the id comes from search but does not add syntax, format, or validation details beyond the schema.

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?

The description states a specific action and resource: retrieve the full text of one document returned by search. It also names document types such as overview, findings, statement, and ratios, but it does not explicitly distinguish this generic `fetch` tool from specialized siblings like `get_company_overview`, `get_findings`, `get_ratios`, or `get_statement`.

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 phrase 'one document that search returned' clearly implies the tool should be used with an id obtained from search. However, the description does not say when to use this tool instead of the specialized sibling tools, nor does it give exclusions or prerequisites.

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

All Annalist Financial Statements 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?