Skip to main content
Glama
Sign In
USAspending MCP Server

USAspending MCP Server

by haydentbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Count New USAspending Awards Over Time

usaspending_new_awards_over_time
Read-onlyIdempotent

Count new federal awards for a specific recipient over time periods such as fiscal year, quarter, or month. Requires recipient hash from USAspending.

Instructions

Count new awards for a specific USAspending recipient over fiscal years, quarters, or months. Requires a recipient_id hash such as values returned by /api/v2/recipient/duns/.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filters": "<filters>"
    },
    "name": "usaspending_new_awards_over_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoquarter
filtersYes
response_formatNoOutput format: markdown for readable summaries, json for raw structured data.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering core behavioral traits. The description adds context about the recipient_id source but does not explain limitations like 'new' award definition, pagination, or zero-count behavior. Overall adequate but not enriched 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?

The description is two sentences with no superfluous words. It front-loads the core purpose and immediately follows with a critical prerequisite. Every sentence earns its place.

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

Completeness2/5

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

Despite the tool's complexity (grouping, date ranges, counting), the description lacks details on return format, definition of 'new awards', or handling of edge cases. No output schema exists, and the openWorldHint is not explained. The description is insufficient for a non-trivial counting tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (33%), and the description only adds meaning for the recipient_id parameter by linking to the DUNS endpoint. The group and response_format parameters are not mentioned, and time_period is not explained beyond its schema description. The description does not compensate for the schema gaps.

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 'Count new awards for a specific USAspending recipient over fiscal years, quarters, or months.' It uses a specific verb ('count') and resource ('new awards'), and implies distinction from sibling tools that handle spending or search. The mention of requiring a recipient_id hash adds specificity.

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 provides a prerequisite (recipient_id hash from another endpoint) but lacks explicit guidance on when to use this tool versus alternatives like usaspending_spending_over_time. It doesn't state when not to use or compare with siblings, only implying usage from the purpose.

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

Deploy Server

Other Tools