Skip to main content
Glama
Sign In

EdgarStack

by com.edgarstack
OverviewDiscussionsAdmin

Summarize SEC-reported capital allocation

analyze_capital_allocation
Read-onlyIdempotent

Summarize SEC-reported operating cash flow, capital expenditures, dividends, common-share repurchases, and shares outstanding by annual or TTM period. Calculates free cash flow, cash returns as a share of positive free cash flow when source inputs are complete, and date-aligned share-count changes. Missing values remain unavailable; outputs describe reported flows and do not judge management decisions or provide financial advice.

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": {
      "ticker": "<ticker>"
    },
    "name": "analyze_capital_allocation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of periods; TTM returns the latest period
periodNoAnnual reported periods or latest trailing twelve monthsannual
tickerYesUS ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: missing values are never imputed ('remain unavailable'), the cash-returns ratio is only computed 'when source inputs are complete', and outputs are scoped to reported flows with no judgment or advice — all of which tell an agent how to interpret partial results.

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?

Three sentences, front-loaded with the metric coverage, then derivations, then data-quality and scope caveats. The enumerated field list is dense but earns its space; the only mild redundancy is repeating 'SEC-reported' framing already conveyed by the title.

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?

With only three parameters, full schema coverage, and no output schema, the description carries the needed burden: it says what is reported, what is derived, and how gaps are handled. The main residual gap is return shape and whether derived metrics are omitted versus flagged when inputs are incomplete, though 'remain unavailable' partially covers this.

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 100%, so ticker, period and limit are already documented, including TTM semantics and the 1-10 limit range. The description only restates 'annual or TTM period' and adds no format or edge-case detail beyond the schema, which is the baseline case.

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 opens with a specific verb and resource ('Summarize SEC-reported operating cash flow, capital expenditures, dividends, common-share repurchases, and shares outstanding') and names the derivation (free cash flow, cash returns ratio, share-count changes). That is enough to separate it from generic siblings like get_financials or compute_ratios, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the capital-allocation/cash-return view rather than a raw financials pull. There is no explicit 'use this instead of X' routing, no note on when TTM is preferable to annual beyond the parameter description, and no stated prerequisites such as the ticker needing SEC coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EdgarStack toolsInspect
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