Skip to main content
Glama

Search US tax-exempt nonprofits by name via the ProPublica

b2b_guidestar
Read-only

Search US tax-exempt nonprofits (IRS Form 990 index) by name via the ProPublica Nonprofit Explorer API: EIN, name, city, state, NTEE code and total result count. Search results only; financial detail pages are not included. GuideStar itself has no free public API, so this uses ProPublica's index. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "b2b_guidestar"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesOrganization name words, 2 to 100 characters
pageNoResult page, 0 or higher (25 results per page)

Output Schema

NameRequiredDescriptionDefault
qNo
pageNo
countNo
sourceNo
checkedAtNo
totalResultsNo
organizationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the cost model ($0.002 per successful call, failed calls not charged), the payment rail (x402 USDC on Base/Solana plus 10 networks), and the provenance caveat that GuideStar has no free public API. These are exactly the facts an agent needs before incurring a paid call.

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 front-loaded sentences with no filler: capability and fields first, scope limitation second, pricing and provenance last. The long parenthetical about payment networks is dense but carries real decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only, paid search tool with an output schema present, the description covers what is searched, what comes back, what is excluded, and what it costs. Nothing an agent needs in order to decide and invoke is missing.

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 description coverage is 100%, so both `q` (2-100 characters) and `page` (25 results per page) are already fully documented in the input schema. The description adds no syntax, format, or matching-behavior detail about the query beyond what the schema states, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Search US tax-exempt nonprofits (IRS Form 990 index) by name' — and names the underlying API (ProPublica Nonprofit Explorer). It also enumerates the returned fields (EIN, name, city, state, NTEE code, total count), so an agent knows exactly what it gets without opening a schema.

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?

Explicitly scopes the tool to 'Search results only; financial detail pages are not included,' which tells the agent when this tool stops being useful. It stops short of naming an alternative for financial detail, so the agent must look elsewhere on its own — a clear context statement but no explicit routing.

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