Skip to main content
Glama

BRAINIAC Grant Compliance

Check supplied eligibility rules

grant-compliance_eligibility-check

Compare each supplied rule with the supplied fact of the same name. A match is not an approval, and missing facts are not filled in. Price $0.04 USDC. POST /api/v1/grant-compliance/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": {
      "rules": "<rules>"
    },
    "name": "grant-compliance_eligibility-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsNo
rulesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it states the matching semantics, warns that a match is not an approval (a critical interpretation guard against over-reading results), and states that missing facts are not filled in, so no inference or defaults occur. It also discloses the paid-access behavior ($0.04 USDC, HTTP 402 blocks execution), which an agent needs before calling; only the result-shape and the disposition of unevaluable rules remain undisclosed.

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 core semantic and caveats before the access/pricing details; nothing is redundant. The three trailing sentences about price, route, and 402 could be tightened into one, which keeps it short of maximal conciseness.

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?

The tool has no output schema and no annotations, so the description must convey both behavior and return expectations. It covers behavior well but never says what comes back per rule (matched/unmatched/unknown) or how unevaluable rules are reported, which is the main question an agent has after calling a checker.

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 for two undocumented parameters. It explains the crucial join semantics — a rule's named fact is matched against the supplied fact of the same name — and the no-fill behavior for absent facts, but leaves the operator enum semantics (what 'includes' or 'boolean_is' match against) and value coercion unaddressed.

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 operation — comparing each caller-supplied rule against the caller-supplied fact of the same name — rather than restating the title. The emphasis on 'supplied' implicitly separates it from the sibling tools that apply built-in domain rules (e.g. expense-eligibility-check), though no sibling is named 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?

There is no explicit when-to-use statement, no when-not-to-use, and no reference to any alternative among the nine related grant-compliance tools. The only hint — that facts must be supplied for rules to be evaluated — is incidental to the behavioral clauses rather than framed as usage guidance.

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