Skip to main content
Glama
Sign In

Nsf Awards

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Awards

search_awards
Read-onlyIdempotent

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": "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

Output Schema

NameRequiredDescriptionDefault
noteYesPagination note about NSF API limits
awardsYes
returnedYesNumber of awards returned in this page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "keyword": "machine learning",
+    "limit": 10,
+    "program": "Algorithms in the Field",
+    "state": "CA"
+  },
+  {
+    "awardee": "MIT",
+    "date_end": "12/31/2023",
+    "date_start": "01/01/2022",
+    "limit": 25,
+    "pi_name": "Smith"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "awards": {
+      "items": {
+        "properties": {
+          "agency": {
+            "description": "Funding agency",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "award_date": {
+            "description": "Award date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "award_id": {
+            "description": "NSF award ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "awardee": {
+            "description": "Awardee institution name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "awardee_city": {
+            "description": "Awardee city",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "awardee_country": {
+            "description": "Awardee country code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "awardee_state": {
+            "description": "Awardee US state code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "cfda_number": {
+            "description": "CFDA program number",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "estimated_total": {
+            "description": "Estimated total award amount",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "expiration_date": {
+            "description": "Award expiration date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "funds_obligated": {
+            "description": "Funds obligated amount",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "nsf_url": {
+            "description": "URL to NSF award search page",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pi": {
+            "description": "Principal Investigator name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "program": {
+            "description": "NSF program name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "start_date": {
+            "description": "Award start date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Award title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "transaction_type": {
+            "description": "Transaction type",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "award_id",
+          "title",
+          "pi",
+          "awardee",
+          "awardee_city",
+          "awardee_state",
+          "awardee_country",
+          "funds_obligated",
+          "estimated_total",
+          "start_date",
+          "expiration_date",
+          "award_date",
+          "agency",
+          "program",
+          "cfda_number",
+          "transaction_type",
+          "nsf_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Pagination note about NSF API limits",
+      "type": "string"
+    },
+    "returned": {
+      "description": "Number of awards returned in this page",
+      "type": "number"
+    }
+  },
+  "required": [
+    "returned",
+    "note",
+    "awards"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. Description adds the return fields (title, PI, etc.), complements annotations without contradiction.

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?

Two sentences: first summarizes purpose and filters, second describes output and alternative. No waste, information is front-loaded.

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

Completeness5/5

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

Given output schema exists, description explains return fields. Covers purpose, filters, returned data, and alternative. Complete for a search tool with rich annotations.

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 coverage is 100% so baseline is 3. Description lists filters but does not add meaning beyond what schema already provides for each parameter.

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?

Description clearly states 'Search NSF awards' and lists all filter criteria. It distinguishes from sibling tool 'get_award' by noting that tool is for full abstract and outcomes report.

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?

Explicitly states when to use this tool (searching) and when to use alternative (get_award for detailed data). Provides clear context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nsf Awards toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources