Annalist Financial Statements

List published snapshots

list_snapshots

Read-onlyIdempotent

Every snapshot that the site has published for a company, oldest first, with its as-of period, dataset hash and time of publication: the point-in-time record of the coverage. Its dates are values of the at parameter of the other tools, which then return the figures as they stood on that date.

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": {
      "company": "<company>"
    },
    "name": "list_snapshots"
  }
}

Input Schema

Name	Required	Description	Default
`company`	Yes	company id from search_companies, for example apple or mizuho

Output Schema

Name	Required	Description	Default
`name`	No
`count`	Yes
`latest`	Yes
`company`	Yes
`snapshots`	Yes
`conventions`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context beyond that: it returns every snapshot, orders results oldest first, and describes the records as point-in-time coverage whose dates feed the at parameter of other tools. It does not disclose pagination or rate-limit behavior, but it is more informative than a baseline safety-only description.

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?

The description is two tight sentences with no wasted language. The core purpose is front-loaded, followed by a useful note about how the returned dates relate to the at parameter of other tools.

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

Completeness5/5

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

Given the one-parameter schema, existing output schema, and read-only annotations, the description is complete enough for correct selection and invocation. It covers what the tool returns, the ordering, and how its output is used by other tools, so no essential information is missing.

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?

There is only one parameter and the schema description coverage is 100%, so the schema already fully documents the company parameter with examples. The description adds only the general phrase 'for a company' and does not contribute additional syntax, format, or constraint details beyond what the schema provides. The baseline score of 3 is appropriate.

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 clearly states a specific verb and resource: listing every published snapshot for a company. It also adds scope and ordering details (company-specific, oldest first, with as-of period, dataset hash, and publication time). It does not explicitly distinguish this from the sibling get_snapshot_info tool, so it falls short of a 5.

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?

The description gives clear usage context by explaining that the returned dates are values for the at parameter of other tools, which then return figures as they stood on that date. It does not state when not to use this tool or explicitly name alternatives such as get_snapshot_info, so no exclusions are provided.

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?