Skip to main content
Glama

BRAINIAC Grant Compliance

Check application completeness

grant-compliance_application-completeness

Mark a requirement present only when an application section cites its id. The answer is not scored, and a complete set is not compliance. Price $0.04 USDC. POST /api/v1/grant-compliance/application-completeness. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "grant-compliance_application-completeness"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionsNo
guidelinesNo
requirementsNo
applicationTextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 disclose key non-obvious behavior: a price of $0.04 USDC, a 402 response with no execution when unpaid, and the important fact that output is not a scored compliance judgment. Remaining gaps are rate limits/retry behavior and the output shape, so it falls short of 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.

Conciseness4/5

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

Four tight sentences with no filler, though the order is unusual: the matching rule leads, caveats follow, and the endpoint path plus pricing trail at the end rather than being grouped as operational metadata. Nothing is wasted.

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?

Given zero annotations, 0% schema coverage, and no output schema, the description does well on payment semantics and the non-compliance disclaimer but leaves both the meaning of two inputs and the shape of the return value unexplained. An agent can call it, but only by guessing at `guidelines` and at what the response contains.

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%, so the description must compensate, and it only clarifies the linkage between a requirement's `id` and a section's `requirementId`. The parameters `guidelines` and `applicationText` receive no explanation at all, leaving half of the inputs undocumented in both schema and description.

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 never plainly states that the tool compares `requirements` against `sections`/`applicationText` to report which requirements are cited; instead it states the matching rule ("Mark a requirement present only when an application section cites its id"). The operation is inferable from the rule plus the name, but the agent must reconstruct the verb+resource itself.

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 when-to-use guidance and no comparison to related siblings such as evidence-match or eligibility-check. The two caveats ("not scored", "a complete set is not compliance") guide interpretation of results, not tool selection or invocation context.

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