Sbir

Sbir Company Awards

sbir_company_awards

Read-onlyIdempotent

Get complete SBIR/STTR award history for a company from www.sbir.gov/awards. Returns all awards with amounts, agencies, topics, and funding phases.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Number of results to return (default 50, max 100).
`company`	Yes	Company name to search for (substring match).

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of awards returned
`awards`	Yes
`company`	Yes	Company name searched

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "company": "Luna",
-    "limit": 50
-  }
-]New value: +[
+  {
+    "company": "RYDBERG",
+    "limit": 5
+  }
+]

changedInput schema / properties / company / description

Previous value: -"Company name to search for"New value: +"Company name to search for (substring match)."

changedInput schema / properties / limit / description

Previous value: -"Number of results to return (default 50)"New value: +"Number of results to return (default 50, max 100)."

Changed1 schema field changedJul 31, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "company": "Acme Technologies Inc.",
-    "limit": 50
-  }
-]New value: +[
+  {
+    "company": "Luna",
+    "limit": 50
+  }
+]

Changed1 schema field changedMay 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "awards": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "company": {
+      "description": "Company name searched",
+      "type": "string"
+    },
+    "count": {
+      "description": "Number of awards returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "company",
+    "count",
+    "awards"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "company": "Acme Technologies Inc.",
+    "limit": 50
+  }
+]

First observedApr 22, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds the source domain and the shape of returned data (amounts, agencies, topics, funding phases), but discloses nothing about truncation, pagination, or empty-result behavior.

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 tight sentences with the purpose front-loaded and the returned fields enumerated second. No filler, no restatement of the title.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile, so the essentials are in place. It is slightly thin on edge behavior (no-match handling, truncation when the company exceeds the limit), which keeps it from a 5.

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 both parameters (limit with default 50/max 100, company substring match) are already fully documented, making 3 the baseline. The description adds no parameter detail and its claim of 'complete' history / 'returns all awards' sits in mild tension with the limit cap, though the schema resolves that ambiguity.

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?

The description gives a specific verb and resource ('Get complete SBIR/STTR award history for a company') and names the data source (www.sbir.gov/awards), which is enough to distinguish a company-scoped lookup from the broader sbir_search_awards or single-award sbir_get_award. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully disambiguating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says whether this should be preferred over sbir_search_awards for a company query, or what happens if the company name is ambiguous. The company scoping is only implied by the tool name and the required 'company' parameter.

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

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.