Skip to main content
Glama

Skillshop

audit_grant_budget

Check a grant budget's math and rules (paid, metered).

budget: {lines: [{category, item, amount, justification, salary?, fte?, months?}], total_request, indirect?: {rate, base: 'tdc'|'mtdc', amount?}, max_indirect_rate?, fringe_rate?, match?: {required_ratio, amount}, participants?}. Checks totals, personnel and fringe math, indirect cap and base, match, missing justifications; returns cost per participant.

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": {
      "budget": "<budget>"
    },
    "name": "audit_grant_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that the tool is paid/metered and enumerates the rule categories it validates (totals, personnel, fringe, indirect cap/base, match, justifications). It never states whether invalid input raises an error or returns a findings list, whether the tool is read-only, or what permissions are needed — a meaningful gap for a mutation-free but cost-bearing call.

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

Conciseness3/5

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

The purpose sentence is front-loaded and the whole thing is short, but the payload is a single dense pseudo-schema line that is hard to parse and mixes nesting with prose. Restructuring the object shape into indented fields would cost no extra words and be far more readable.

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?

Because an output schema exists, the description need not detail return values, and it covers nearly everything else an agent needs: the input object's structure, the checks performed, and the cost model. It is only thin on failure behavior and prerequisites, which are not covered by annotations either.

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

Parameters4/5

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

Schema coverage is 0% and the budget parameter is a bare object with additionalProperties, so the description is the only field documentation available — and it delivers a full shape: lines with category/item/amount/justification/salary/fte/months, total_request, indirect with rate/base enum/amount, max_indirect_rate, fringe_rate, match, participants. Some semantics remain ambiguous (units for required_ratio, meaning of 'base' values), which keeps it below a 5.

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 opens with a specific verb and resource: 'Check a grant budget's math and rules', and adds the return value ('cost per participant'). It implicitly separates itself from audit_grant_proposal by scoping to the budget document, but it never names or contrasts a sibling explicitly.

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 only usage signal is the parenthetical '(paid, metered)', which tells the agent about cost rather than when to call it. Nothing says which situations warrant a budget audit versus a proposal audit, nor whether a budget must first exist or be in a draft state.

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.

Resources