Skip to main content
Glama
HappyMonkeyAI

OpenUSPublicDataMCP

search_usaspending_awards

Search federal spending awards by keyword to retrieve award details from USAspending.gov, with customizable result limits.

Instructions

Search federal spending awards by keyword through USAspending.gov.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries full burden for behavioral traits. It mentions 'by keyword' but omits details on pagination, rate limits, data freshness, or what constitutes a keyword (e.g., award title, description). The output schema exists but is not summarized.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is very short, but it under-specifies the tool's functionality. Conciseness should not sacrifice necessary information.

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

Completeness1/5

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

Given the lack of schema descriptions, no annotations, and an output schema that is not described, the description is severely incomplete. The agent will be missing critical information to use the tool effectively.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description does not explain either parameter. 'query' is implied by 'by keyword', but 'limit' is not mentioned at all. No constraints or formats are described.

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 clearly states the tool searches federal spending awards by keyword via USAspending.gov, which distinguishes it from sibling tools like search_congress_bills or search_federal_register. However, it lacks any additional nuance or detail about the scope of search.

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?

No guidance is provided on when to use this tool versus alternatives, when not to use it, or any prerequisites. The description simply states what it does without context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HappyMonkeyAI/OpenUSPublicDataMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server