Skip to main content
Glama

get_earnings_quality_benchmark

Read-only

Earnings quality and financial statement risk benchmarks — accruals ratio, cash conversion, and revenue recognition risk by sector. Source: SEC EDGAR aggregate + Sloan accruals model (academic standard). For CFOs, auditors, and analysts assessing financial reporting risk before M&A or investment. $0.02 USDC per call.

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": {
      "sector": "<sector>"
    },
    "name": "get_earnings_quality_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYes
revenue_recognition_modelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the data provenance (SEC EDGAR aggregate plus the Sloan accruals model) and a per-call price of $0.02 USDC, which matters for cost-aware agents. It does not describe freshness/lag of the EDGAR aggregates or the shape of the returned benchmark, leaving some behavioral gaps.

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 compact sentences, front-loaded with what the tool returns, then provenance, then audience and price. No filler; the only mild inefficiency is that the audience clause and the price clause could be tighter, but both earn their place.

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?

For a two-parameter read-only benchmark lookup with no output schema, the definition covers the essentials: metric coverage, data source, methodology, target user, and cost. The main omission is any indication of output structure or sector coverage limits, but an agent has enough to call it correctly.

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 parameter meaning. It implies the sector dimension ('by sector') and gestures at revenue recognition via 'revenue recognition risk', and both enums are self-describing. However, it never explains that revenue_recognition_model is optional or how it changes the benchmark, so the second parameter's semantics remain thin.

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?

Names a specific resource (earnings quality / financial statement risk benchmarks) and enumerates the concrete metrics returned: accruals ratio, cash conversion, revenue recognition risk, segmented by sector. That is far more specific than the sibling pattern of 'get_X_benchmark', though it never explicitly contrasts itself with neighbors like get_audit_fee_benchmark or get_asc_benchmark.

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?

Gives a clear use context — CFOs, auditors, and analysts assessing reporting risk before M&A or investment — which tells an agent when this tool is the right pick. It stops short of naming exclusions or pointing to alternative tools when the need is, say, audit fees rather than accruals quality.

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