Skip to main content
Glama

Annalist Financial Statements

Get a company

get_company
Read-onlyIdempotent

One company in one call: by default its overview (its latest figures and measures, its key findings with their documents, its peers and a summary of its lenders, customers, suppliers and owners). include adds any of findings (the key findings of the latest snapshot), history (every record of the findings ledger), events (corporate events), quality (withheld and restated values), snapshots (every published version with its time), info (units, sign conventions, fiscal calendar), documents (the source documents) and relationships; at gives the snapshot that was the latest on a date. The answer names whether the company reports quarters or fiscal years only and its latest period, available lists the parts not in the answer, and not_included states what the answer leaves out and the call that gives it.

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

Input Schema

NameRequiredDescriptionDefault
atNoan ISO date: the snapshot that was the latest on that date, in place of the latest snapshot
limitNoentries of a part that lists values, such as quality (default 50)
companyYesthe company of a search result (apple), its id from fetch (company:apple), or a ticker or CIK
includeNothe parts of the answer (default overview, or info with at)

Output Schema

NameRequiredDescriptionDefault
infoNo
nameYes
as_ofNo
eventsNo
companyYes
historyNo
qualityNo
reportsNo
citationYes
findingsNo
includedYes
overviewNo
snapshotYes
availableYes
documentsNo
snapshotsNo
conventionsNo
not_includedYes
latest_periodNo
relationshipsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add shape and it does: it discloses the default payload, that include replaces/extends it, how at overrides the latest snapshot, and that responses self-document via available and not_included. It doesn't mention size limits or truncation beyond limit's schema default, which keeps it off a 5.

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

Conciseness3/5

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

The core purpose is front-loaded, but the body is one long run-on sentence with nested parentheticals that is hard to parse. The overview parenthetical and the include list of parts overlap somewhat, and the available/not_included clauses are near-duplicative, so trimming is possible.

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?

For a four-parameter read tool with full schema coverage and an output schema, this covers everything an agent needs: defaults, date semantics, expansion options, and how to discover what was omitted. The self-describing available/not_included fields even remove the need to guess at response shape.

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 every parameter is already documented there, so the baseline applies; the description does add meaning for include by explaining what each value yields and for at by stating it substitutes for the latest snapshot. That is helpful but largely restates the enum names, so it earns the baseline rather than clearly above it.

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?

"One company in one call" names the verb and the resource and then enumerates the default payload (latest figures, key findings with documents, peers, counterparties), so an agent knows exactly what comes back. It partially differentiates from siblings by pointing at fetch for the company id, but it never routes against get_series, compare_companies or screen_companies, so it stops 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?

It gives clear in-tool guidance: use include to add parts, use at to get the snapshot that was latest on a date, and note that at defaults include to info. What's missing is any statement of when to prefer this over a sibling (e.g., get_series for a single measure, compare_companies for multi-company work).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources