Nsf Awards

Get Award

get_award

Read-onlyIdempotent

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`award_id`	Yes	NSF award ID (numeric string)

Output Schema

TableJSON Schema

Name	Required	Description
`pi`	Yes	Principal Investigator name
`co_pi`	Yes	Co-PI names
`title`	Yes	Award title
`agency`	Yes	Funding agency
`awardee`	Yes	Awardee institution name
`nsf_url`	Yes	URL to NSF award search page
`program`	Yes	NSF program name
`abstract`	Yes	Award abstract
`award_id`	Yes	NSF award ID
`pi_email`	Yes	PI email address
`award_date`	Yes	Award date
`start_date`	Yes	Award start date
`cfda_number`	Yes	CFDA program number
`awardee_city`	Yes	Awardee city
`publications`	Yes	Research and conference publications
`awardee_state`	Yes	Awardee US state code
`awardee_address`	Yes	Awardee full address
`awardee_country`	Yes	Awardee country code
`estimated_total`	Yes	Estimated total award amount
`expiration_date`	Yes	Award expiration date
`funds_obligated`	Yes	Funds obligated amount
`outcomes_report`	Yes	Project outcomes report
`performance_zip`	Yes	Performance ZIP code
`performance_city`	Yes	Performance city
`transaction_type`	Yes	Transaction type
`performance_state`	Yes	Performance state code
`performance_location`	Yes	Performance location

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "award_id": "2147483647"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "abstract": {
+      "description": "Award abstract",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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_address": {
+      "description": "Awardee full address",
+      "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"
+      ]
+    },
+    "co_pi": {
+      "description": "Co-PI names",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "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"
+      ]
+    },
+    "outcomes_report": {
+      "description": "Project outcomes report",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "performance_city": {
+      "description": "Performance city",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "performance_location": {
+      "description": "Performance location",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "performance_state": {
+      "description": "Performance state code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "performance_zip": {
+      "description": "Performance ZIP code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pi": {
+      "description": "Principal Investigator name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pi_email": {
+      "description": "PI email address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "program": {
+      "description": "NSF program name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "publications": {
+      "description": "Research and conference publications",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "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",
+    "pi_email",
+    "co_pi",
+    "performance_location",
+    "performance_city",
+    "performance_state",
+    "performance_zip",
+    "awardee_address",
+    "abstract",
+    "outcomes_report",
+    "publications"
+  ],
+  "type": "object"
+}

First observedMay 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. Description adds value by detailing the returned content (abstract, outcomes report, PI info), going beyond annotations.

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?

Single sentence with no wasted words, clearly and efficiently conveys the tool's function.

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 the presence of an output schema and clear single-parameter input, the description sufficiently covers what the tool does and returns.

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% with clear description for award_id. Description adds 'by ID' but no additional meaning beyond schema, so baseline 3 is appropriate.

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 it fetches a single NSF award by ID, with specific resources (abstract, outcomes, PI info), distinguishing it from sibling search_awards which likely handles multiple awards.

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?

The description implies use for fetching a single award, but does not explicitly state when not to use it or suggest alternatives like search_awards for multiple awards.

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

All Nsf Awards tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.