Skip to main content
Glama

Stratalize Intelligence

Get Earnings Quality Benchmark

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
Behavior4/5

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

Annotations already cover readOnlyHint/openWorldHint/destructiveHint, so the safety profile is set; the description then adds genuinely new context: the data provenance ('SEC EDGAR aggregate + Sloan accruals model') and a per-call price of $0.02 USDC, which matters for cost-sensitive tool selection. It does not describe granularity, refresh cadence, or what a null/empty sector result 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 most important content (what metrics, by what segmentation) is front-loaded in the first clause, and the sentence set is tight with no filler. The price and audience sentences are short and each adds distinct information, though the em-dash list format is slightly dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description responsibly names the three metric families a caller gets back, which is the key completeness requirement here. However, it leaves the second parameter entirely unexplained and gives no sense of result shape (per-sector single row vs. per-company comparisons), which is a real gap for a benchmarking tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 burden, and it does not: 'revenue_recognition_model' is never mentioned, and 'sector' is only implied by the phrase 'by sector'. Both are enums, so their allowed values are visible in the schema, but the description adds no meaning about how the optional revenue-recognition filter changes the benchmark comparison.

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 states a specific verb+resource ('Earnings quality and financial statement risk benchmarks') and enumerates the actual metrics returned: accruals ratio, cash conversion, and revenue recognition risk by sector. It implicitly separates itself from siblings like get_audit_fee_benchmark or get_esg_benchmark by naming a distinct analytical domain, though it never names a sibling explicitly.

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 a concrete usage context ('assessing financial reporting risk before M&A or investment') and names the intended audience (CFOs, auditors, analysts), which tells an agent when this tool is the right pick. It does not say when NOT to use it or point to any alternative benchmark tool, so it stops short of full routing guidance.

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