Skip to main content
Glama

beatandraise.com SEC Filings

Verify a Quote or Figure

verify_quote
Read-onlyIdempotent

Check that a figure or sentence really appears in a filing document, and get a link that highlights exactly where.

Use this before stating any number or quotation from a filing. Analysts need to see the figure in the source; a link to the whole document is not enough. Quote the text as it appears in the document: a sentence, or a table row's label and figure ("Total net sales 416,161", "Gross margin 75.0%"). Words and numbers must match exactly. Spacing, table-cell breaks, "$" and curly quotes may differ.

Returns found (true/false) and, for each occurrence, its surrounding context, a highlight_url (beatandraise.com viewer, marks that exact span, including across table cells), to cite with the quotation. If there are several occurrences, pick the one whose context fits the claim, or quote more of the row to pin one. If found is false, do not present the text as a quotation from this document: numbers_elsewhere shows where its figures do appear, which usually reveals a misremembered figure or the wrong document. A label and a figure ("Operating income 79,975") are rarely adjacent in a table, where other years' columns sit between them: a miss on one returns try_instead, the verify_figure call that checks the number however the row is laid out. Use verify_figure for figures.

Args: cik: CIK of the filer (e.g. "0000320193") accession_number: SEC accession number (e.g. "0000320193-25-000079") filename: The document the text came from (e.g. "aapl-20250927.htm", or an exhibit such as "q4fy26cfocommentary.htm"), as listed in content_object or in a search result quote: The exact text to find (max 1000 characters)

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>",
      "filename": "<filename>",
      "quote": "<quote>"
    },
    "name": "verify_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYes
quoteYes
filenameYes
accession_numberYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description goes well beyond that. It discloses the response shape (found, per-occurrence context, highlight_url, numbers_elsewhere, try_instead), the exact-match matching rules and their tolerated exceptions (spacing, table-cell breaks, dollar signs, curly quotes), and the practical failure mode (label and figure rarely adjacent in a table). No contradiction with the read-only annotations.

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?

Purpose and the core 'use before citing' rule are front-loaded, and the Args block is scannable. Some content is redundant: verify_figure is introduced twice, and the closing 'Use verify_figure for figures' duplicates the preceding sentence about try_instead, adding length without new information.

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?

Although an output schema exists, the description still explains how to read the key return fields (which occurrence to pick, what numbers_elsewhere implies, when try_instead fires), which is what an agent needs to act on results. Nothing required to call it correctly – document selection, exact quoting, fallback path – is missing.

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 all parameter meaning, and it does: it gives CIK and accession-number formats with examples, explains what filename must refer to and where it comes from (content_object or a search result, including exhibit files), and defines quote as exact text capped at 1000 characters with concrete acceptable quoting styles.

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 opening sentence names a specific verb and resource: check that a figure or sentence appears in a filing document and return a highlighting link. It is distinguishable from siblings like search_document and check_citations. It loses a point because the scope wobbles: the tool claims to verify 'a figure or sentence' but later instructs 'Use verify_figure for figures', so the agent must resolve which tool owns numeric figures.

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?

Explicit when-to-use ('Use this before stating any number or quotation from a filing', analysts need the source span, not a whole-document link), explicit when-not ('If found is false, do not present the text as a quotation'), and an explicit alternative ('Use verify_figure for figures', plus the try_instead fallback for label+figure rows). It even tells the agent how to disambiguate among multiple occurrences.

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