Grants Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | The Simpler Grants API key used to authenticate the requests |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-grantsC | Search for government grants based on keywords |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search-grants' has a clear, distinct purpose that cannot be confused with any other tool in the set.
The single tool name 'search-grants' follows a consistent verb-noun pattern, and with only one tool, there is no inconsistency or deviation to evaluate. The naming is straightforward and predictable.
A single tool for a grants search server feels thin and under-scoped. While search is a core function, typical grant-related workflows might include operations like filtering, sorting, or retrieving details, making one tool insufficient for comprehensive coverage.
The tool set is severely incomplete for a grants search domain. It only provides a basic search function, with obvious gaps such as no ability to view grant details, filter by criteria, or manage saved searches, which are essential for effective agent interaction.