grant-finder
Server Details
Find federal and public grants a business may qualify for, with eligibility and links.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 1 of 1 tools scored.
Only one tool exists, so no confusion between tools. The tool's purpose is clearly defined with a detailed description, leaving no ambiguity for an agent.
The single tool name, 'find_grants', follows a clear verb_noun pattern. Since there is only one tool, naming consistency is inherently maintained.
With only one tool, the server feels thin for typical tool surfaces. However, the tool comprehensively covers the domain of grant finding, so it is arguably well-scoped but on the low end.
The tool provides a complete solution for finding grants, covering multiple funding sources and eligibility assessment. There are no obvious missing operations for the stated purpose of discovering open funding opportunities.
Available Tools
1 toolfind_grantsAInspect
Find REAL, currently-open funding (federal grants from Grants.gov, SBIR/STTR R&D programs, plus curated foundation grants, accelerators, and business-plan competitions) that a small business, startup, nonprofit, or individual plausibly QUALIFIES for. Returns matched opportunities each with: title, funder, amount, an HONEST eligibility verdict (likely/maybe/unlikely + why), deadline, a sober competitiveness/odds note, and the official application link. Never guarantees an award. Data is live and public.
| Name | Required | Description | Default |
|---|---|---|---|
| flags | No | Self-declared eligibility flags: woman, veteran, minority, tribal, rural, student. | |
| limit | No | Max matches (default 15). | |
| naics | No | Optional NAICS code. | |
| stage | No | Business stage. | |
| state | No | Two-letter US state, e.g. 'TX'. | |
| interests | No | Industry/interests free text, e.g. 'biotech, clean energy'. | |
| entityType | No | What the applicant is. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description carries full burden. It declares data is 'live and public' and explicitly states 'Never guarantees an award.' Does not disclose rate limits or authentication needs, but provides honest eligibility and competitiveness notes. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is a single paragraph of 4-5 sentences, front-loaded with core purpose. Concise and informative without excessive length. Slight improvement possible with bulleted output fields, but overall effective.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 7 optional parameters, no output schema, and no annotations, the description is very complete. It explains input parameters implicitly via context, describes return fields in detail, and includes caveats about eligibility and no guarantee. Meets needs for agent invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds overall context but does not elaborate on individual parameters beyond what's in the schema. Each parameter already has a clear schema description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool finds 'REAL, currently-open funding' for specific entities, with detailed output components. Distinguishes itself by mentioning sources (Grants.gov, SBIR/STTR, etc.) and honest eligibility verdict. No sibling tools provided, but the purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use (for small businesses, startups, nonprofits, individuals seeking funding) and what it returns. Includes caveat 'Never guarantees an award.' Lacks explicit 'do not use when' or alternative tool references, but with no siblings, guidance is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!