Sbir

Sbir Get Award

sbir_get_award

Read-onlyIdempotent

Get full details for one SBIR/STTR award, identified by its contract number or agency tracking number (the award_id/contract fields returned by sbir_search_awards). SBIR has no lookup-by-id endpoint, so this searches and verifies the identifier matches — start from sbir_search_awards rather than guessing an id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`award_id`	Yes	Contract number or agency tracking number, exactly as returned in `award_id` or `contract` by sbir_search_awards.

Output Schema

TableJSON Schema

Name	Required	Description
`city`	No	City location
`phase`	No	Funding phase
`state`	No	2-letter state code
`agency`	Yes	Funding agency code
`branch`	No	Agency branch or division
`company`	Yes	Company name
`program`	No	SBIR/STTR program type
`abstract`	No	Award abstract or summary
`award_id`	No	Unique award identifier
`award_year`	No	Year award was made
`topic_code`	No	Topic or program code
`award_title`	Yes	Title of the award
`award_amount`	No	Award amount in dollars

Schema Changelog

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

Changed2 schema fields changedJul 31, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "award_id": "2024-DOD-SB241-001"
-  }
-]New value: +[
+  {
+    "award_id": "W911NF-22-C-0033"
+  }
+]

changedInput schema / properties / award_id / description

Previous value: -"The unique award ID"New value: +"Contract number or agency tracking number, exactly as returned in `award_id` or `contract` by sbir_search_awards."

Changed1 schema field changedMay 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "abstract": {
+      "description": "Award abstract or summary",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "agency": {
+      "description": "Funding agency code",
+      "type": "string"
+    },
+    "award_amount": {
+      "description": "Award amount in dollars",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "award_id": {
+      "description": "Unique award identifier",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "award_title": {
+      "description": "Title of the award",
+      "type": "string"
+    },
+    "award_year": {
+      "description": "Year award was made",
+      "type": [
+        "number",
+        "string",
+        "null"
+      ]
+    },
+    "branch": {
+      "description": "Agency branch or division",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "city": {
+      "description": "City location",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "company": {
+      "description": "Company name",
+      "type": "string"
+    },
+    "phase": {
+      "description": "Funding phase",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "program": {
+      "description": "SBIR/STTR program type",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "state": {
+      "description": "2-letter state code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "topic_code": {
+      "description": "Topic or program code",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "company",
+    "agency",
+    "award_title"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "award_id": "2024-DOD-SB241-001"
+  }
+]

First observedApr 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate a safe, read-only, idempotent operation. The description adds valuable behavioral context beyond that: it reveals that there is no direct lookup endpoint and that the tool performs a search and verification under the hood. This helps set expectations about performance and potential failures. A minor gap is not mentioning what happens if the identifier is not found, but the output schema likely covers that.

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 two sentences, front-loaded with the primary purpose and immediately followed by critical usage guidance. Every word is purposeful; no filler or redundancy.

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?

For a single-parameter, read-only tool with an output schema, the description is complete. It explains the identifier, the lack of a direct lookup endpoint, the need to start from sbir_search_awards, and the verification behavior. The output schema handles return expectations, so nothing else is needed.

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. The description reinforces the meaning of award_id as a contract number or agency tracking number and emphasizes that it must match the fields from sbir_search_awards, but it does not add new semantic detail beyond the schema's own description. The added context about verification is more behavioral than parameter-focused.

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 clearly states the verb ('Get full details') and the resource (one SBIR/STTR award), and it distinguishes itself from siblings by specifying the identifier type and the fact that it searches and verifies rather than directly looking up. It explicitly references sbir_search_awards as the source for the identifier.

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?

The description gives explicit when-to-use guidance: start from sbir_search_awards rather than guessing an id. It also explains why (no lookup-by-id endpoint) and that the tool searches and verifies the identifier, which effectively tells the agent that this tool is for getting details after a search, not for initiating a search.

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

All Sbir 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.