Skip to main content
Glama

BRAINIAC Construction Site Operations

Parse construction daily reports

construction-site-operations_daily-report-parse

Copy supplied daily reports into structured rows with dates, locations, authors, workforce, and referenced activities. Delay wording is flagged as recorded narrative only. Price $0.04 USDC. POST /api/v1/construction-site-operations/daily-report-parse. 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_daily-report-parse"
  }
}

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

B3.1/5.0
Behavior3/5

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

With no annotations, the description usefully discloses the operational profile: pricing ($0.04 USDC), the POST endpoint, and that unpaid calls return 402 without running. It also states that delay wording is flagged as narrative rather than interpreted. It stops short of describing side effects, permissions, or what the response looks like.

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, purpose front-loaded, with endpoint and pricing information kept tight. Little waste, though the price and endpoint could arguably be structured elsewhere; overall it reads cleanly.

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, nested-object tool with no annotations and no output schema, the description is thin. It omits the required input shape and the relationship among the many optional arrays, so an agent cannot confidently construct a correct call from the description 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?

Twelve parameters exist at 0% schema description coverage, and the description explains none of them. It names extracted fields but never clarifies the input alternatives (csv vs json vs text vs file) or how the reports/activities/delays/rfis/deliveries/instructions arrays should be supplied, leaving most of the input contract undocumented.

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 concrete verb ('copy ... into structured rows') and resource ('supplied daily reports'), and enumerates the output fields extracted (dates, locations, authors, workforce, referenced activities). This distinguishes it from analytical siblings like delay-event-detect, though it does not name any sibling 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?

Usage is implied by the phrase 'supplied daily reports' and the note that delay wording is treated as narrative only, which hints it does not compute delay impact (that is delay-event-detect's job). There is no explicit when-to-use/when-not guidance or prerequisites beyond the payment note.

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