Skip to main content
Glama

BRAINIAC Construction Site Operations

Report site operations

construction-site-operations_report

Combine daily reports, progress deviations, recorded and inferred delays, RFIs, instructions, deliveries, and change comparisons from supplied site records. Price $0.12 USDC. POST /api/v1/construction-site-operations/report. 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_report"
  }
}

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 usefully discloses commercial and failure behavior: price of $0.12 USDC, the POST endpoint, and that unpaid calls return 402 without running. That is real operational context an agent cannot get from structured fields. However, it says nothing about whether the operation is read-only/computational, what the report output contains, or how partial/malformed input records are handled.

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?

Three short sentences, front-loaded with the core capability, followed by billing and endpoint facts. No filler; the only mild inefficiency is that price and endpoint repeat metadata an agent may already have, but they earn their place for a paid API.

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 12-parameter, deeply nested tool with no output schema and no annotations, the description is too thin: it does not clarify the four mutually exclusive input formats, the asOf anchor, or what the combined report returns. An agent can identify the tool's intent but cannot confidently construct a correct call from this text alone.

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% across 12 parameters, so the description must carry the burden and largely does not. It never explains that csv, json, text, and file are alternative input channels for the same records, nor what asOf or scope mean, though the listed record types loosely map to the array parameters (reports, delays, rfis, instructions, deliveries, activities).

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 uses a specific verb ('Combine') and enumerates the exact record types consumed: daily reports, progress deviations, delays, RFIs, instructions, deliveries, change comparisons. This clearly positions it as the aggregate/rollup tool relative to the single-domain siblings, but it never explicitly says it is the alternative to calling the individual analyzers.

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 / when-not-to-use guidance and no routing to or from siblings such as progress-analyze or delay-event-detect. The phrase 'from supplied site records' hints that the caller must gather and pass the data rather than the tool fetching it, but that is inference, not stated 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