Skip to main content
Glama

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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate write safety. It instead adds behavior the annotations cannot convey: the upstream data source (ProPublica Nonprofit Explorer), a per-call price of $0.10 USDC, and a cryptographic attestation with a verification URL. Cost and provenance are exactly the kind of extra context an agent needs before invoking a metered external call.

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 definition leads with the returned data fields, then provenance, then a use case, then trust and pricing, so the most decision-relevant content is front-loaded. Each sentence is short and informative, though the attestation and pricing lines read slightly promotional and could be compressed.

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?

The description sensibly enumerates the returned metrics, which compensates for the absence of an output schema and makes the tool's output shape legible. However, for a lookup keyed on a single free-text organization name, it is silent on matching behavior, ambiguity handling, and what a not-found response looks like, leaving a real gap for a one-parameter retrieval 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?

The schema's 0% coverage leaves org_name entirely undocumented, and the description does not compensate at all: it never says whether org_name is a legal name, a partial/fuzzy match, a DBA, or an EIN. With only one parameter and no description of its accepted form, an agent can easily call this incorrectly.

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 resource (IRS Form 990 nonprofit financials) and enumerates the concrete fields returned: revenue, expenses, net assets, program expense ratio, executive compensation, revenue trend, and health signal. That is far clearer than the tool name alone. It does not explicitly contrast itself with siblings such as get_irs_industry_tax_statistics, so it stops short of a 5.

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?

The phrase 'Essential for evaluating nonprofit health systems, universities, and foundations' implies the domain where the tool applies, but it never says when to call this instead of a sibling tool or what input conditions are required. Usage is inferred rather than stated, which is the definition of a 3.

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