Skip to main content
Glama

BRAINIAC Grant Compliance

Extract grant deadlines

grant-compliance_deadline-extract

Read Deadline lines that contain a YYYY-MM-DD date. Other dates in the guidelines are not turned into deadlines. Price $0.03 USDC. POST /api/v1/grant-compliance/deadline-extract. 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": {
      "guidelines": "<guidelines>"
    },
    "name": "grant-compliance_deadline-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
guidelinesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does supply real operational context: price of $0.03 USDC, the POST endpoint, and the failure mode where unpaid calls return 402 and do not execute. What's missing is what a successful call returns (no output schema exists) and whether the operation is purely read-only in effect — 'Read' hints at it but the HTTP POST verb complicates that inference.

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, with the extraction rule front-loaded ahead of pricing and transport details. Nothing is padded, though the fragmentary pricing/endpoint sentences read as boilerplate rather than integrated guidance.

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 one-parameter tool with no output schema and no annotations, the description covers cost, endpoint, and payment failure but leaves the return shape entirely unexplained — an agent cannot tell whether it receives a list of dates, line references, or structured deadline objects. That is a material gap given nothing else documents the response.

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 coverage is 0%, so the description must compensate for the single 'guidelines' parameter. It only implies the parameter via 'Other dates in the guidelines', giving no detail on expected format beyond the pattern rule, no hint about the 50,000-character limit, and no clarification that the whole guidelines document is the input.

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 verb and resource ('Read Deadline lines') and defines the matching rule precisely: only lines containing a YYYY-MM-DD date become deadlines, other dates are excluded. That scope detail alone separates it from the other grant-compliance extract/validate siblings, 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 Guidelines3/5

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

The extraction condition ('Deadline lines that contain a YYYY-MM-DD date') implicitly tells an agent when this tool applies versus not applying, but there is no explicit when-to-use guidance, no mention of the requirements-extract sibling, and no stated prerequisites about what the guidelines text should contain.

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