Skip to main content
Glama

BRAINIAC Construction Site Operations

Track requests for information

construction-site-operations_request-for-information-track

Track RFI asked/due/answered dates and identify unresolved or overdue items from supplied statuses. Contractual entitlement is not decided. Price $0.04 USDC. POST /api/v1/construction-site-operations/request-for-information-track. 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": "construction-site-operations_request-for-information-track"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
rfisNo
textNo
scopeNo
delaysNo
reportsNo
activitiesNo
deliveriesNo
instructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses pricing, the POST endpoint, unpaid-call behavior (402 and no execution), and the contractual-entitlement limit, but it does not describe return values, side effects, or whether supplied data is stored.

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?

The description is short and front-loads the purpose before boundaries and payment details. Every sentence adds useful information, though the endpoint path is somewhat redundant with the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 12 params, nested objects, no annotations, and no output schema, the description is too thin. It explains purpose and payment behavior but leaves input format choices, parameter semantics, and expected output shape largely undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 12 parameters with 0% description coverage, and the description does not explain any of them—not csv/json/text/file input modes, asOf, rfis, scope, delays, reports, activities, deliveries, or instructions. It mentions asked/due/answered/status conceptually but adds essentially no parameter-level meaning beyond the schema names.

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 gives a specific verb and resource: track RFI asked/due/answered dates and identify unresolved or overdue items. It is clear enough to distinguish this from sibling tools such as delay-event-detect or daily-report-parse, though it does not explicitly compare itself to them.

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?

It implies the use case—tracking RFI dates and finding unresolved or overdue items—and includes one clear scope boundary: contractual entitlement is not decided. It does not name alternatives or state when another sibling tool should be used instead.

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