Skip to main content
Glama
datanexusmcp

DataNexus MCP

Official
by datanexusmcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

nonprofit_search_nonprofits_by_name

Read-onlyIdempotent

Find US nonprofits by name and state to retrieve EIN, revenue, and NTEE codes. Returns up to 25 matches.

Instructions

Search US nonprofits by name with optional state filter. Read-only. No side effects. Idempotent. US only. Returns up to 25 matches. name: Full or partial organisation name. Required. state: Two-letter US state code e.g. CA, NY. Optional, defaults to all states. Returns EIN, name, state, revenue, and NTEE code for each match. Use this when you have a name but not the EIN. Use nonprofit_fetch_nonprofit_by_ein instead when you have the exact EIN for a precise single lookup. Verified source: IRS EO BMF. 7-day cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="nonprofit_search_nonprofits_by_name", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesOrganization name to search e.g. Red Cross. Required.
stateNoTwo-letter US state code e.g. CA. Optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.16
    • addedInput schema / properties / name / description
      Added value: +"Organization name to search e.g. Red Cross. Required."
    • addedInput schema / properties / state / description
      Added value: +"Two-letter US state code e.g. CA. Optional."
  2. Addedv2.1.8
  3. Removedv2.1.7
  4. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds 'No side effects', 'US only', 'Returns up to 25 matches', '7-day cache', and 'Verified source: IRS EO BMF', providing rich behavioral context beyond annotations.

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 description is well-structured, starting with purpose, then parameter details, usage guidance, and fallback instruction. However, it is slightly verbose due to repetition of annotation-provided traits like 'Read-only. No side effects. Idempotent.' and inclusion of a feedback mechanism that could be separate.

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 simple search tool, the description covers all relevant behavioral aspects: idempotency, caching, source, output fields, limits, and alternatives. The output schema exists, so return values are not needed in description. Complete for the context.

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 coverage is 100% with descriptions for both parameters. The description adds clarity by stating 'Full or partial organisation name' for name and 'Optional, defaults to all states' for state, which are not explicit in the schema.

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?

The description clearly states the verb (search), resource (nonprofits), and scope (US by name with optional state filter). It distinguishes from sibling tools like fetch_nonprofit_by_ein and search_nonprofits_by_category by specifying when to use each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool (when you have a name but not EIN) and when to use the alternative (fetch_nonprofit_by_ein). Also provides context on idempotency, US-only, limit of 25 matches, and a fallback feedback mechanism.

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

Deploy Server

Other Tools