Skip to main content
Glama

beatandraise.com SEC Filings

Verify a Figure

verify_figure
Read-onlyIdempotent

Check that a number you are about to state appears in a filing, however it is written.

Every number is compared as its digits alone (separators, decimal point, sign, $ and % dropped, zeros trimmed): "416,161", "416.161" and "416,161,000" are all 416161. Your figure must be one of the filing's numbers times a power of ten, allowing for rounding to the digits you give: "$416.2 billion" matches 416,161 (in millions), "75%" matches "75.0 %". Searches every document in the filing (main document and exhibits) unless filename is given. Candidates are ranked by exactness and by your label's words appearing in the number's row label or lead-in text.

Returns found, match_count, and up to 10 matches, each with its document, label, context and a highlight_url that marks that exact number in the beatandraise.com viewer. Matching ignores magnitude, so confirm each candidate's label, period and scale from its context, then cite its highlight_url. found=false means no number in the filing has those digits: do not attribute the figure to the filing. If you calculated it (a growth rate, a margin), say so and cite the inputs instead. found=null with checked=false means nothing was checked, which says nothing about the figure: a structured XML form (Form 3/4/5, 144, D, 13F) has no text to check, so read its values with get_document and cite that; the note says what to do.

Args: cik: CIK of the filer (e.g. "0000320193") accession_number: SEC accession number value: The figure as you would state it (e.g. "$416.2 billion", "75.0%", "-1,234"). A value with one significant digit ("$10.00", "20,000,000") only matches numbers written exactly the same way; "$2 million" is too vague to check. label: What the figure is (e.g. "total net sales", "GAAP gross margin"). Used for ranking. filename: Optional single document to check instead of the whole filing

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": {
      "cik": "<cik>",
      "accession_number": "<accession_number>",
      "value": "<value>"
    },
    "name": "verify_figure"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYes
labelNo
valueYes
filenameNo
accession_numberYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description goes well beyond the annotations by explaining the digit-normalization comparison, power-of-ten matching, rounding allowances, ranking behavior, search scope, return fields, highlight_url semantics, and the meaning of found=false and found=null with checked=false. These are substantial behavioral details that help the agent interpret results correctly.

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 front-loaded with the core purpose and then organized into matching rules, return behavior, and argument notes. It is long, but most detail is necessary for a complex verification tool; a little tightening could still improve scannability.

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 complex matching semantics, the output schema, and the annotations, the description is complete enough for an agent to call the tool and interpret both positive and negative results. It also handles edge cases like calculated figures and structured XML filings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 parameter burden. It describes all five arguments, including examples for cik and value, the special matching caveat for one-significant-digit values, the ranking use of label, and the scoping effect of filename.

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

Purpose5/5

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

The description states a specific verb and resource: checking that a stated number appears in a filing, with explicit scope over main document and exhibits. It is clearly distinguishable from tools like verify_quote or check_citations by focusing on numeric figures in filings.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance before stating a number, when-not guidance for calculated figures, and an alternative path for structured XML forms using get_document. It also explains what found=false means so the agent knows not to attribute the figure to the filing.

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