USASpending.gov

get_idv_funding

Read-only

List File C funding records associated with an IDV.

Rows can identify the IDV itself as well as associated awards; they are
not a complete list of child orders. File C coverage can be partial or
lagged and does not establish the full child-order obligation or amount
paid. Use get_idv_amounts() for reported child-order obligation totals
and get_idv_activity() or get_idv_children() for child-order records.

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_funding"
  }
}

Input Schema

Name	Required	Default
`page`	No
`sort`	No	reporting_fiscal_date
`limit`	No
`order`	No	desc
`award_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds important behavioral caveats beyond annotations: File C coverage may be partial or lagged, rows are not a complete list of child orders, and the data does not establish the full child-order obligation or amount paid. Those limitations are exactly what an agent needs to avoid overinterpreting the result.

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 front-loaded with the tool's scope, then immediately gives data caveats and routing alternatives. Every sentence earns its place, and there is no redundant restatement of the title or annotations.

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?

The description is strong for a read-only listing tool with an output schema: it explains the data source, caveats, and sibling alternatives. However, for a tool with five parameters and 0% schema description coverage, it omits pagination and sorting semantics, which are relevant to calling the list tool correctly. The remaining gap is modest because defaults and enums are visible in the schema.

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 0%, so the description must compensate for undocumented parameters, but it does not mention award_id, page, sort, limit, or order at all. The schema supplies types, defaults, and enums for sort and order, but the description adds no meaning about how award_id is interpreted or how pagination and sorting affect the result. This leaves the parameter guidance significantly incomplete.

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 File C funding records associated with an IDV." It also distinguishes this tool from nearby IDV siblings by explicitly naming get_idv_amounts, get_idv_activity, and get_idv_children. An agent can identify the tool's scope without opening the schema.

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?

The description gives explicit alternatives and the conditions that select them: get_idv_amounts for reported child-order obligation totals, and get_idv_activity or get_idv_children for child-order records. It also warns that these rows can identify the IDV itself as well as associated awards, which clarifies when this list is and is not the right source.

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.