Skip to main content
Glama

BRAINIAC Grant Compliance

Check expenses against supplied rules

grant-compliance_expense-eligibility-check

Apply only the supplied category decisions. A category with no rule stays not supplied, and an eligible rule is not a funder decision. Price $0.04 USDC. POST /api/v1/grant-compliance/expense-eligibility-check. 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": {
      "expenses": "<expenses>",
      "rules": "<rules>"
    },
    "name": "grant-compliance_expense-eligibility-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesYes
expensesYes

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?

With no annotations, the description does real work: it discloses pricing ($0.04 USDC), the failure mode (402 on unpaid calls, which do not run), and a semantic caveat that an eligible rule is not a funder decision. It still omits whether the call mutates state, what the response contains, and limits on rules/expense counts.

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?

Sentences are short, front-loaded with the core constraint, and every one carries a distinct fact (scope, unmatched behavior, verdict semantics, cost, endpoint, payment failure). The telegraphic style is dense but not padded.

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?

For a paid, unannotated tool with no output schema and 0% parameter coverage, the description covers cost and payment failure well but leaves the return shape and input field semantics unexplained. An agent knows what it costs and what won't count as eligible, but not exactly what it gets back.

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% for the two parameters, so the description must compensate, and it largely does not. It hints that rules are keyed by category and that missing rules produce a "not supplied" outcome, but never explains the expenses array structure, the amount/description fields, or the accepted decision values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says to "Apply only the supplied category decisions," which implies a rules-vs-expenses evaluation, but it never names the resource (expenses) explicitly and gives no basis for choosing it over the sibling grant-compliance_eligibility-check. The title carries most of the differentiation, which the description should not rely on.

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?

The phrase "Apply only the supplied category decisions" functions as a scoping constraint, and the note that unmatched categories "stay not supplied" implies the call is rule-driven rather than inference-driven. There is no explicit statement of when to use this rather than the sibling eligibility-check tools, and no preconditions on the rules set.

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