Skip to main content
Glama

beatandraise.com SEC Filings

Compare Filing Item With Prior Year

compare_filing_item
Read-onlyIdempotent

What changed in one Item of a 10-K, 10-Q or 20-F since the same filing a year earlier (new and dropped risk factors, rewritten MD&A, legal proceedings...), shown to the user as a marked-up comparison in the viewer.

You get every added, removed and changed paragraph as text: inside a changed one, [-old words-] and {+new words+}. Unchanged paragraphs are left out of your copy. The prior filing is the company's same form filed closest to one year before (a 10-Q is compared with the same quarter last year); pass prior_accession_number to choose another. Changes are numbered; a long list comes in pages: the last line says to call more_item_changes for the next one.

Args: accession_number: The newer filing (10-K, 10-Q or 20-F) item: The Item, by number or name ("1A", "Risk Factors", "7", "MD&A", "3") part: 10-Q only: "I" or "II" when the number exists in both parts ("1", "2"); Risk Factors is Part II Item 1A prior_accession_number: Optional. The older filing to compare with

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": {
      "accession_number": "<accession_number>",
      "item": "<item>"
    },
    "name": "compare_filing_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
partNo
accession_numberYes
prior_accession_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the actual payload: added, removed and changed paragraphs as text with [-old words-] and {+new words+} markers, unchanged paragraphs omitted, changes numbered, and long lists paged. This is exactly the kind of context annotations cannot carry.

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 purpose and comparison basis come first, then the return format, then pagination, then the args block. Every sentence adds operational information about format, defaults, or paging; there is no filler.

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?

With no output schema and zero schema coverage, the description must explain both return shape and parameter meaning, and it does both while also covering the default comparison logic and paging. An agent has everything needed to call this correctly on the first attempt.

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 fully carries parameter meaning and does so: it explains that item accepts a number or name with examples ('1A', 'Risk Factors', '7', 'MD&A'), that part is 10-Q-only with 'I'/'II' for ambiguous numbers and notes Risk Factors is Part II Item 1A, and that prior_accession_number is the optional older filing.

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 opens with a specific verb-and-resource framing: 'What changed in one Item of a 10-K, 10-Q or 20-F since the same filing a year earlier,' with concrete examples (new/dropped risk factors, rewritten MD&A, legal proceedings). An agent can distinguish this from a plain item reader like get_filing_item purely from the text.

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 states the default comparison target precisely (same form filed closest to one year prior; a 10-Q compared with the same quarter last year) and tells the agent how to override it via prior_accession_number. It also routes pagination to more_item_changes. It stops short of an explicit 'use this instead of get_filing_item when...' statement, so a 4 rather than 5.

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