Skip to main content
Glama

Sbir

by io.github.pipeworx-io
OverviewAdmin

Sbir Agency Stats

sbir_agency_stats
Read-onlyIdempotent

Get SBIR/STTR award counts by agency. Specify agency (e.g., "DOD", "NASA", "NSF") or omit to see all major agencies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agencyNoSpecific agency to count, e.g. "DOW" (formerly DOD), "NASA", "NSF". Omit to cover all major agencies. Note SBIR publishes no total-count field, so a result at the page cap reports `award_count_at_least` rather than a total.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "agency": "DOD"
-  },
-  {}
-]New value: +[
+  {
+    "agency": "DOW"
+  },
+  {}
+]
    • changedInput schema / properties / agency / description
      Previous value: -"Specific agency to get count for (e.g., \"DOD\", \"NASA\"). Omit to get counts for all major agencies."New value: +"Specific agency to count, e.g. \"DOW\" (formerly DOD), \"NASA\", \"NSF\". Omit to cover all major agencies. Note SBIR publishes no total-count field, so a result at the page cap reports `award_count_at_least` rather than a total."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "oneOf": [
+    {
+      "properties": {
+        "agency": {
+          "description": "Agency code",
+          "type": "string"
+        },
+        "award_count": {
+          "description": "Total award count for agency",
+          "type": "number"
+        }
+      },
+      "required": [
+        "agency",
+        "award_count"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "agencies": {
+          "items": {
+            "properties": {
+              "agency": {
+                "description": "Agency code",
+                "type": "string"
+              },
+              "award_count": {
+                "description": "Total award count for agency",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "error": {
+                "description": "Error message if retrieval failed",
+                "type": "string"
+              }
+            },
+            "required": [
+              "agency"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "agencies"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "agency": "DOD"
+  },
+  {}
+]
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive, so the description need not restate safety. The description adds no extra behavioral detail beyond that; the page-cap caveat ('award_count_at_least') appears only in the parameter schema, not the main description. No contradiction with 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?

The description is two concise sentences: the first states the core purpose, the second explains parameter usage with examples. No filler or redundant content, front-loaded with the primary action.

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?

For a simple read-only stats tool with one optional parameter, an output schema, and full annotations, the description adequately sets expectations. It could mention the page-cap behavior for context, but that is already captured in the parameter schema, so overall completeness is good.

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% for the single 'agency' parameter, so the baseline is 3. The description repeats examples already present in the schema and does not add new semantic depth. The schema itself provides the 'DOW' (formerly DOD) detail and the page-cap caveat, so the description adds little beyond the structured data.

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 'Get SBIR/STTR award counts by agency' using a specific verb and resource. It distinguishes itself from sibling tools like sbir_search_awards or sbir_company_awards by focusing on counts by agency, and gives concrete examples ('DOD', 'NASA', 'NSF').

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool: to get counts by agency, with guidance to specify an agency or omit to see all major agencies. It does not explicitly mention alternatives or exclusions, but the purpose is distinct enough among siblings.

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

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

Resources