Skip to main content
Glama

BRAINIAC Grant Compliance

Match evidence to requirements

grant-compliance_evidence-match

Attach evidence that cites a requirement id. Evidence with no id is not matched, and the strength of the evidence is not judged. Price $0.05 USDC. POST /api/v1/grant-compliance/evidence-match. 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": {
      "requirements": "<requirements>"
    },
    "name": "grant-compliance_evidence-match"
  }
}

Input Schema

NameRequiredDescriptionDefault
evidenceNo
requirementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that evidence strength is not judged, the $0.05 USDC price, the POST endpoint, and that unpaid calls return 402 without executing. The notable gap is the return shape — no output schema exists and the description never says what a match result looks like.

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?

Four short sentences, front-loaded with the operation and its main caveat; pricing and transport details follow. Every sentence carries information, though the endpoint path and price phrasing read like boilerplate appended to the core definition.

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, two-array tool with no annotations and no output schema, the definition covers input semantics and billing behavior but leaves the response contract entirely unspecified, which an agent needs in order to use the result.

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. It explains the meaning of the optional evidence[].requirementId field ('evidence that cites a requirement id', unmatched without it), which is genuinely useful, but says nothing about the required requirements array, its item shape, or the 40/80 item caps.

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?

States a specific action on a specific resource: 'Attach evidence that cites a requirement id', matching the title 'Match evidence to requirements'. The verb drifts between 'attach' and 'match', but the core operation (linking evidence to requirements by id) is unmistakable and distinguishable from the sibling extract/validate tools.

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

Usage Guidelines4/5

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

Gives an explicit exclusion rule: evidence without a requirement id is not matched, so an agent knows what input will silently do nothing. It does not name any alternative tool or state prerequisites (e.g. requirements must be extracted first), which keeps it short of a 5.

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