Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__get_award

Fetch a single NSF award by ID. Returns full abstract, project outcomes report (if completed), and detailed PI/awardee info.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "award_id": "2147483647"
    },
    "name": "nsf-awards__get_award"
  }
}

Input Schema

NameRequiredDescriptionDefault
award_idYesNSF award ID (numeric string)

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?

With no annotations provided, the description carries the full disclosure burden. It does useful work by naming the returned payload (full abstract, project outcomes report if completed, PI/awardee details), implying a read-only operation, but it says nothing about behavior when the ID does not exist, whether the outcomes report field is absent versus empty, or any auth/rate-limit constraints.

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?

Two short sentences, front-loaded with the action and followed by the return summary. No filler or redundancy, though it is terse enough that a sentence of usage context could have been added without bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description's return-value summary is doing real work and covers the main payload components. For a one-parameter lookup tool this is nearly complete; the only gap is edge-case behavior (award not found, absent outcomes report).

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter, including the 'numeric string' format and an example, so the schema already documents everything. The description adds only the words 'by ID', which does not go beyond the schema. Baseline 3 applies.

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 verb and resource ('Fetch a single NSF award by ID') and implicitly distinguishes itself from any list/search variant by the word 'single'. No sibling tool is named for differentiation, which keeps it short of a 5.

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?

Usage is implied by the required award_id: call it when you already have an NSF award ID and need the full record. There is no explicit when-not guidance, no mention of an alternative for searching by keyword or PI name, and no note on what to do when the ID is unknown.

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.