Annalist Financial Statements

Get a company overview

get_company_overview

Read-onlyIdempotent

One answer on a company, the first call for a question about it: identity, sector, latest snapshot, revenue and net income of the latest quarter (or fiscal year) with their change against a year earlier, the latest value of each measure of the directory (margins, returns, growth, debt, liquidity) with its period and unit, the current key findings with their source document ids, 3 peers, data quality, its relationships in Atlas (the count of its lenders, customers, suppliers, owners and holdings, the largest of each, and what the documents do not state) and links to the page and the workbook.

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_overview"
  }
}

Input Schema

Name	Required	Description	Default
`company`	Yes	company id from search_companies, for example apple or telkom-indonesia

Output Schema

Name	Required	Description	Default
`more`	No
`name`	Yes
`as_of`	Yes
`links`	No
`peers`	Yes
`checks`	No
`latest`	Yes
`market`	No
`sector`	No
`company`	Yes
`country`	No
`sources`	No
`tickers`	No
`citation`	Yes
`exchange`	No
`findings`	Yes
`industry`	No
`measures`	Yes
`snapshot`	Yes
`template`	No
`documents`	No
`accounting`	No
`data_quality`	No
`published_at`	No
`relationships`	Yes
`fiscal_year_end`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026

addedOutput schema / properties / relationships

Added value: +{
+  "properties": {
+    "counts": {
+      "type": "object"
+    },
+    "largest": {
+      "type": "object"
+    },
+    "more": {
+      "type": "string"
+    },
+    "not_stated": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "counts",
+    "largest",
+    "not_stated"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "company",
-  "name",
-  "snapshot",
-  "as_of",
-  "latest",
-  "measures",
-  "findings",
-  "peers",
-  "citation"
-]New value: +[
+  "company",
+  "name",
+  "snapshot",
+  "as_of",
+  "latest",
+  "measures",
+  "findings",
+  "peers",
+  "relationships",
+  "citation"
+]

AddedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, and closed-world behavior, so the description does not need to restate safety. It adds useful behavioral context by disclosing that the overview includes data quality, source document ids, fixed peer coverage, relationship counts, and explicitly surfaces what the documents do not state.

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 description is front-loaded with the key routing statement, but it is a single very dense sentence enumerating many return fields. Because an output schema exists, much of that enumeration is redundant, and the run-on structure makes it harder to scan than it needs to be.

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 one-parameter read-only overview tool with annotations and an output schema, the description is substantially complete: it establishes the first-call role and describes the breadth of the response. It could be stronger with explicit guidance on which sibling tools to use for narrower follow-ups.

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 already documents it fully with an example company id. The description adds no additional parameter semantics, so 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 states a specific resource (a company) and positions the tool as the broad first-call overview, then enumerates the domains it covers. It distinguishes itself functionally from specialized siblings such as get_ratios or get_findings by being the comprehensive entry point, though it does not name those siblings explicitly.

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 phrase 'the first call for a question about it' gives clear when-to-use guidance for an agent starting on a company. It does not state when not to use it or explicitly name alternative tools for narrower follow-up questions, so it falls short of full alternative routing guidance.

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?