Skip to main content
Glama

beatandraise.com SEC Filings

More Item Changes

more_item_changes
Read-onlyIdempotent

The next page of a compare_filing_item result: its changes from number changes_from on. Pass the same arguments as the compare_filing_item call, and the changes_from its last line gives.

Args: accession_number: As in compare_filing_item item: As in compare_filing_item changes_from: From the previous page's last line part: As in compare_filing_item prior_accession_number: As in compare_filing_item

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>",
      "changes_from": "<changes_from>"
    },
    "name": "more_item_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
partNo
changes_fromYes
accession_numberYes
prior_accession_numberNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-redundant behavior: this is a cursor-style continuation keyed to the last line of the prior result, which tells the agent the call is stateless and repeatable with the same arguments. It stops short of describing what an exhausted or empty page looks like.

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 key fact — that this is the next page of a named sibling — is front-loaded in the first sentence, and the total length is small. The Args block is largely a restatement of parameter names already present in the schema, which is mild waste but not disruptive.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. For a five-parameter pagination tool the remaining meaningful gaps are minor: the description never says what happens when there are no further changes, and it does not clarify whether the inherited arguments must match the original call exactly or only in part.

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 description coverage is 0%, so the description must carry the load; it clarifies changes_from (an integer carried over from the previous page's last line) but for the other four parameters it only says 'As in compare_filing_item', delegating meaning rather than supplying it. That delegation is useful for correct invocation but adds no semantics about what those values are or their formats.

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 — it returns 'the next page of a compare_filing_item result' — and immediately disambiguates it from the sibling compare_filing_item by framing it as the continuation rather than the primary call. The offset semantics ('its changes from number changes_from on') make the scope unambiguous.

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 explicit invocation guidance: pass the same arguments as compare_filing_item and take changes_from from the previous page's last line. What it leaves implicit is the trigger condition — how an agent knows a further page exists — but the follow-up protocol itself is clearly spelled out.

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