nsf-awards-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_nsf_awardsB | Search NSF awards and funding. Returns {total, items}. |
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 confusion between tools. The tool's purpose is clearly described as searching NSF awards.
The single tool name 'search_nsf_awards' follows a clear verb_noun snake_case convention, which is consistent with standard MCP naming practices and predictable.
At one tool, the server feels thin, but it is scoped to a specific search function. This is borderline for the stated purpose of searching NSF awards and funding.
The search tool covers the primary need, but there are minor gaps such as lacking a direct 'get award by ID' endpoint. Agents can work around this by searching for and retrieving specific items from the results.