Skip to main content
Glama
Sign In

Usaspending

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Usa Incumbent Profile

usa_incumbent_profile
Read-onlyIdempotent

Federal contract portfolio for one contractor -- "what does Leidos hold and when does it expire", "which of Booz Allen's contracts come up for recompete", incumbent research before a bid. Returns active award count, total obligated, ceiling, expirations at 6/12/18 months, top agencies and NAICS, and the next awards to expire with dates.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 5,
      "recipient": "Booz Allen"
    },
    "name": "usa_incumbent_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many upcoming expirations to list (default 10, max 100).
recipientYesContractor name, substring match (e.g. "Leidos", "Booz Allen").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark it read-only, idempotent, and non-destructive, so the safety burden is covered. The description adds useful behavioral detail about the aggregation output and time-based expiration breakdowns (6/12/18 months), and nothing contradicts the 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?

Two sentences; the first scopes and motivates, the second enumerates return fields. Every clause carries signal and there is no duplication of schema content.

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 read-only query tool with two parameters and no output schema, the description explains what is returned and in what analytical frame, which is enough to call it correctly. It could have disambiguated from sibling tools like usa_recipient_profile or usa_expiring_awards, but this is a minor gap.

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%, with 'recipient' and 'limit' already described including default/max and substring matching. The description reinforces the single-contractor role but does not add new parameter-level detail beyond the schema baseline.

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 opens with a concrete object ('Federal contract portfolio for one contractor') and gives question-style examples that scope it immediately. The returns list ('active award count, total obligated, ceiling...') makes the tool's operation concrete and distinguishes it from broader award-search tools.

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?

It provides clear context: use for a single contractor's holdings and expirations, explicitly tied to 'incumbent research before a bid.' It does not explicitly name alternative siblings or exclusion cases, so it stops short of a full 5.

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

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

Resources