Skip to main content
Glama

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. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior, and the description adds real value beyond them: data provenance (IRS Statistics of Income, actual filed returns rather than survey estimates), the specific metrics returned, and a per-call cost of $0.50 USDC. It does not disclose the reference period or data recency, which matters for a statistical benchmark.

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?

Front-loaded with the 'Use when…' trigger before mechanics, and the worked example is genuinely useful for calibrating output. Minor waste from restating the same point twice ('most authoritative source' and 'actual filed returns, not survey estimates') and from promotional phrasing.

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 no output schema, the description carries the return-value burden and does so by naming the metrics and giving a numeric sample. Two gaps remain: no reference period or data vintages for the statistics, and no explanation of what 'entity_type: all' broadens to.

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 coverage is 50%: 'industry' is documented in-schema and the Healthcare example clarifies the expected value format. The 'entity_type' enum (corporation/all) is completely unaddressed in the description, and the phrase 'corporation income tax returns' only implicitly signals the default, leaving the 'all' option undefined.

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?

States a specific verb and resource: returns IRS SOI aggregate statistics from filed corporation income tax returns, covering gross receipts, net income margins, and effective tax rates by industry. The domain is distinctive enough to separate it from neighbors like get_irs_990_intelligence or get_industry_spend_benchmark, 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 Guidelines4/5

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

Provides four concrete use cases up front (benchmarking against industry tax data, valuation comparables for M&A, effective-tax-rate comparison by sector, due diligence context). That is clear when-to-use guidance, but it offers no when-not conditions or named alternative tools for adjacent needs.

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