Skip to main content
Glama

Stratalize Intelligence

Get Irs Industry Tax Statistics

get_irs_industry_tax_statistics
Read-only

Use when benchmarking financial performance against industry-level tax return data, establishing valuation comparables for M&A, assessing typical effective tax rates by sector, or producing financial due diligence context from the most authoritative source of actual US business financial performance. Returns IRS SOI aggregate statistics from actual filed corporation income tax returns — gross receipts, net income margins, and effective tax rates by industry. Data reflects actual filed returns, not survey estimates. Example: Healthcare and Social Assistance — 284,000 returns, 8.3% net income margin, 19.1% effective tax rate, $4.2M average gross receipts per return — baseline for healthcare PE valuation and acquisition multiples analysis. Source: IRS Statistics of Income Division. $0.50 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": {
      "industry": "<industry>"
    },
    "name": "get_irs_industry_tax_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryYesIndustry name or NAICS sector (e.g. healthcare, construction, professional services, manufacturing)
entity_typeNocorporation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the data provenance (actual filed returns, not survey estimates), the specific metric set returned, and an explicit per-call cost of $0.50 USDC — the cost disclosure in particular is context an agent cannot get from annotations. It does not discuss caching, freshness/lag of the SOI data, or coverage limits by entity type.

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?

It is front-loaded with the 'Use when...' clause and then moves to output content, provenance, a worked example, and cost — a sensible order. The illustrative example with figures is longer than strictly necessary but earns its place by showing the output shape and typical magnitude, which no output schema provides.

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 lookup with no output schema, the description covers the return content, the data source, the cost, and typical values, so an agent knows what to expect back. The remaining hole is the entity_type semantics and whether industry accepts free-form names or NAICS codes robustly; the schema hints at NAICS but the description adds nothing there.

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 only 50%: 'industry' is documented in the schema and reinforced by the Healthcare example in the description, but 'entity_type' is defined only by an enum and default with no explanatory text anywhere. The description never explains what 'all' means versus 'corporation' (e.g. whether it includes S-corps, partnerships, or sole proprietorships), which is exactly the gap the description should have closed.

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 names a specific verb and resource: it returns IRS SOI aggregate statistics from actual filed corporation income tax returns, with named metrics (gross receipts, net income margins, effective tax rates) and a named data source. The 'corporation income tax returns' phrasing implicitly separates it from the nonprofit-focused 990 sibling, but no alternative is explicitly named, so sibling differentiation is left to inference.

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 clear when-to-use context: benchmarking financial performance, establishing valuation comparables for M&A, assessing effective tax rates by sector, and financial due diligence. What is missing is any exclusion or named alternative — it does not say when to prefer a different benchmark tool or when this data is inappropriate (e.g. for pass-through entities).

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