Skip to main content
Glama

990.tax nonprofit lookup

Nonprofit rankings

get_top_nonprofits
Read-onlyIdempotent

Ranked lists from e-filed Form 990 returns, national (25) or per state (10): highest-paid executives, largest by revenue, most money raised, richest by net assets, biggest employers.

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": {
      "list": "<list>"
    },
    "name": "get_top_nonprofits"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYes
limitNoDefault 10
stateNoTwo-letter US state or territory code, e.g. TX

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the data provenance ('e-filed Form 990 returns') and the list-size constraint, but says nothing about entry shape, ranking basis, or whether results are cached or paginated.

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?

A single dense sentence that front-loads the data source and then enumerates categories and the size constraint. No filler, though the 'national (25) or per state (10)' shorthand requires a moment to parse.

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?

For a three-parameter read tool with no output schema, the definition covers what to request but not what comes back (e.g., whether entries include name, EIN, revenue amount, or rank). An agent can invoke it correctly but cannot anticipate the response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, and the description adds real meaning beyond the schema: it clarifies that national lists go up to 25 while state-scoped lists go to 10, which explains the `limit` maximum=25 and why it may effectively be capped lower when `state` is supplied. The `list` enum values are paraphrased in prose but not individually described.

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 resource (ranked lists from e-filed Form 990 returns) and enumerates the five ranking categories that map to the `list` enum (highest-paid executives, largest by revenue, top fundraising, richest by net assets, biggest employers). An agent can tell this is a rankings tool, though it doesn't explicitly contrast itself with siblings like get_nonprofit_stats or search_nonprofits.

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 parenthetical 'national (25) or per state (10)' implies the selection rule for the `state` parameter, which is genuinely useful usage context. However, there is no explicit when-to-use/when-not guidance or named alternative tool for cases where the agent wants a profile, stats, or a free-text search.

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