Skip to main content
Glama

BRAINIAC Grant Compliance

Validate a grant budget

grant-compliance_budget-validate

Sum the supplied lines, compare that sum with a supplied total, and check supplied category amount or percent caps. No cap is assumed. Price $0.05 USDC. POST /api/v1/grant-compliance/budget-validate. Unpaid calls return 402 and do not run.

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": {
      "lines": "<lines>"
    },
    "name": "grant-compliance_budget-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYes
totalNo
limitsNo
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries real weight and discloses the commercial and transport behavior: price of $0.05 USDC, the POST endpoint, and that unpaid calls return 402 and do not execute. That 402/no-execution detail is exactly the kind of pre-call behavior an agent needs. It does not say whether the operation is read-only/idempotent or how failures are signaled, which keeps it below a 5.

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?

Four short sentences, front-loaded with the operation, then the default-cap rule, then price/endpoint/payment behavior. Every sentence carries information an agent needs before invoking; no restatement of the name or filler.

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?

There is no output schema, so the description should describe what comes back, but it does not say whether the result is a boolean, a per-line/per-cap violation list, or numeric deltas. Combined with the unmentioned currency parameter and unspecified total-vs-sum mismatch behavior, an agent knows how to call it but not what to expect back.

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 must compensate, and it partially does: lines are described as summed, total as the comparison target, and limits as category amount or percent caps with none assumed by default. The currency parameter is never mentioned, and nothing explains what a mismatch between the sum and total produces or how caps relate to the raw amount versus percent of total.

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 gives a specific three-part operation: sum the lines, compare to a supplied total, and check supplied category caps. That is more precise than the title alone, and the mechanics (sum vs. caps vs. total) distinguish it from a generic report validator. It never states the domain purpose (grant budget compliance), relying on the name to carry that.

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

Usage Guidelines3/5

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

Usage is only implied through the mechanics: pass a total to reconcile, pass limits to enforce caps, and note that 'No cap is assumed' when limits are omitted. There is no explicit statement of when to reach for this versus a sibling such as grant-compliance_report-validate, and no prerequisites or preconditions are described.

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