Skip to main content
Glama

get_idv_funding_rollup

Read-only

Funding rollup totals for an IDV (single dict, not paginated).

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

Input Schema

NameRequiredDescriptionDefault
award_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the useful detail that the result is a single unpaginated dict, but says nothing about error behavior, a missing/unknown award_id, or empty-result handling.

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?

A single, front-loaded sentence with the return shape in parentheses; nothing is wasted. It is appropriately tight for a one-parameter read tool.

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

Completeness3/5

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

An output schema exists and the annotations carry the safety profile, so the description needn't explain return fields. Still, for a tool in a dense sibling set, it omits both param meaning and sibling differentiation, leaving real gaps an agent must guess around.

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 coverage is 0%, so the description must carry the burden of explaining award_id, but it says nothing about it. It doesn't clarify whether this is an IDV/award identifier, its expected format, or what happens if it refers to a non-IDV award.

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 states a specific resource ('funding rollup totals for an IDV') with an implied verb and explicitly notes the return shape ('single dict, not paginated'). However, it does not differentiate from the closely related siblings get_idv_funding, get_idv_funding, and especially get_award_funding_rollup, so an agent must still infer which one to reach for.

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?

The phrase 'not paginated' implies a usage context (retrieve the whole rollup in one call), but there is no explicit when-to-use, no exclusions, and no routing to alternatives like get_idv_funding or get_award_funding_rollup. In a crowded IDV namespace this leaves the choice ambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.