USASpending.gov

get_idv_activity

Read-only

List child task/delivery orders awarded under an IDV.

Results are ALWAYS sorted by obligated amount, descending; the endpoint
accepts no sort or order parameters. (Earlier releases exposed sort/order
here, but the API silently ignored them: the advertised default of
period_of_performance_start_date was never the actual ordering. Round 10
audit finding.) For date-ordered children use get_idv_children(), whose
endpoint does honor sort/order.

hide_edge_cases=True filters out child awards missing obligated/awarded
amounts or end dates.

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": {
      "award_id": "<award_id>"
    },
    "name": "get_idv_activity"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`limit`	No
`award_id`	Yes
`hide_edge_cases`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the non-obvious always-descending obligated-amount ordering and the fact that sort/order parameters are ignored. It also explains exactly what hide_edge_cases=True filters out.

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

Conciseness4/5

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

The purpose and the key sorting/alternative guidance are front-loaded and useful. The historical audit note and parenthetical provenance are somewhat verbose, but the core content earns its place.

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?

Given an output schema and safety annotations, the description covers the critical behavioral traits: sorting, ignored parameters, sibling alternative, and edge-case filtering. It is nearly complete, with the main gap being explicit pagination semantics for page and limit.

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 0%, so the description should compensate. It fully explains hide_edge_cases and implies that award_id is the IDV identifier, but page and limit are left undocumented despite being non-obvious pagination controls.

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 states a specific verb and resource: list child task/delivery orders awarded under an IDV. It also distinguishes this tool from the sibling get_idv_children by explaining that this endpoint is not date-ordered while get_idv_children is.

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

Usage Guidelines5/5

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

It explicitly routes date-ordered use cases to get_idv_children() and warns that this endpoint accepts no sort/order parameters. That gives the agent a clear when-to-use-this-vs-alternative rule.

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

All USASpending.gov 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.