Skip to main content
Glama

Stratalize Intelligence

Get Irs 990 Intelligence

get_irs_990_intelligence
Read-only

IRS Form 990 nonprofit financial data — total revenue, expenses, net assets, program expense ratio, executive compensation, revenue trend, and financial health signal. Source: ProPublica Nonprofit Explorer. Essential for evaluating nonprofit health systems, universities, and foundations. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.10 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": {
      "org_name": "<org_name>"
    },
    "name": "get_irs_990_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=true, destructive=false, openWorld=true). The description adds genuinely useful non-schema behavior: the upstream data source (ProPublica Nonprofit Explorer), a per-call price of $0.10 USDC, and a cryptographic settlement receipt with a verification URL — all of which affect an agent's cost/trust calculus. It stops short of stating what happens for unmatched or ambiguous organization names.

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 data payload in a compact fragment list, then source, audience, attestation, and price. Each sentence roughly earns its place, though 'Essential for evaluating...' and the pricing/attestation line lean promotional rather than operational.

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 correctly compensates by enumerating the returned fields, and it discloses source and cost. The remaining gap is input-matching behavior — how org_name is resolved when the name is ambiguous or unknown — which is the one thing an agent could realistically get wrong here.

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% for the single parameter org_name, so the description carries the full explanatory burden — and it says nothing about it. An agent cannot tell whether org_name expects a legal name, a DBA, an EIN, or whether fuzzy matching is performed, despite the 2–200 character constraint hinting at free-text name matching.

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 the exact resource (IRS Form 990 nonprofit financials) and enumerates the returned metrics — total revenue, expenses, net assets, program expense ratio, executive comp, revenue trend, health signal — so an agent knows precisely what comes back. It does not differentiate itself from adjacent siblings such as get_irs_industry_tax_statistics, so the agent must infer which IRS-family tool applies.

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?

'Essential for evaluating nonprofit health systems, universities, and foundations' supplies a usage context, which is better than nothing. But it gives no when-not conditions, no prerequisites (e.g., is an EIN or exact legal name required), and no explicit routing to alternative tools when the subject isn't a nonprofit.

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