Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__search_awards

Search NSF awards. Filter by keyword (matches title/abstract), PI name, awardee institution, NSF program, date range, US state, or country. Returns title, PI, awardee, amount, dates, program. Use get_award for full abstract + outcomes report.

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": {
      "limit": 10,
      "state": "CA",
      "keyword": "machine learning",
      "program": "Algorithms in the Field"
    },
    "name": "nsf-awards__search_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page (1-25, default 25, NSF max)
stateNoAwardee US state code (e.g., "CA")
offsetNoPagination offset (default 1)
awardeeNoAwardee institution name
countryNoAwardee country code (e.g., "US")
keywordNoSearch term (title + abstract)
pi_nameNoPI full or last name
programNoNSF program name (e.g., "Algorithms in the Field")
date_endNoAward start date <= MM/DD/YYYY
date_startNoAward start date >= MM/DD/YYYY

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully states which fields are returned and that keyword matches title/abstract, but it does not explicitly state read-only behavior, pagination behavior, or result limits beyond what the schema supplies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences, front-loaded with the main action and followed by filters, return fields, and the key alternative. Every sentence carries useful information with no filler.

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?

Given ten optional parameters, complete schema coverage, no output schema, and no annotations, the description covers the core search behavior, the return summary, and the handoff to get_award. It omits pagination and read-only details, but the schema supplies pagination parameters and the tool's search nature is clear.

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%, so the parameter descriptions already define each filter. The description adds only a brief clarification that keyword searches title and abstract, which the schema also states, and does not add syntax or usage guidance beyond 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 states a specific verb and resource ('Search NSF awards'), lists the filter dimensions, and identifies the summary fields returned. It also distinguishes the tool from get_award, which is for full abstracts and outcomes reports.

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?

It explicitly tells the agent to use get_award when full abstract and outcomes report are needed, making the main alternative and its selection condition clear. The search use case is implicit in the first sentence and supported by the listed filters.

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.