Propublica Nonprofit

Propublica Nonprofit Get Filing

propublica_nonprofit_get_filing

Read-onlyIdempotent

Get a specific IRS filing for a nonprofit. Returns financial data from one tax period including revenue, expenses, assets, and liabilities. Example: get_filing(131710957, 202112).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ein": 131710957,
      "tax_period": 202112
    },
    "name": "propublica_nonprofit_get_filing"
  }
}

Input Schema

Name	Required	Description	Default
`ein`	Yes	Employer Identification Number
`tax_period`	Yes	Tax period in YYYYMM format (e.g., 202112 for December 2021)

Output Schema

Name	Required	Description
`ein`	Yes	Employer Identification Number
`filing`	Yes
`organization_name`	Yes	Organization name

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds that a filing covers a single tax period and summarizes the financial categories returned, but says nothing about missing periods, latency, or partial data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: purpose, payload, then a concrete example. The purpose is front-loaded and nothing is redundant.

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 an output schema present, return-value explanation is optional, and two fully documented parameters make this a simple tool to call. The only real omission is whether a filing may not exist for a given ein/period.

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 100%, and both parameters carry their own descriptions including the YYYYMM format. The worked example reinforces argument order and value shape but adds no semantics beyond the schema.

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?

Names a specific verb and resource: 'Get a specific IRS filing for a nonprofit', scoped to one tax period. This clearly separates it from an organization-level lookup like get_organization, though it never states that distinction explicitly.

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?

Usage is only implied by the required ein + tax_period pairing; there is no statement of when to reach for this versus get_organization or any other retrieval tool, and no prerequisites or failure conditions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Propublica Nonprofit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.