Skip to main content
Glama

BRAINIAC Construction Site Operations

Detect construction delay events

construction-site-operations_delay-event-detect

Collect recorded delay rows and daily-report delay wording, and separately label impacts inferred from baseline versus actual dates. Liability is not determined. Price $0.04 USDC. POST /api/v1/construction-site-operations/delay-event-detect. 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_delay-event-detect"
  }
}

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
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose valuable operational facts — price ($0.04 USDC), the POST endpoint, and that unpaid calls return 402 without executing — but says nothing about whether the operation is read-only, what it returns, or how inputs are combined or prioritized.

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?

Front-loaded with the purpose, then the scope caveat on liability, then cost/endpoint/payment behavior. Compact and mostly waste-free; the endpoint path is somewhat redundant but harmless.

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 analysis tool with no annotations and no output schema, the description is thin. It never explains the expected return structure, how the different input sources interact, or how the inferred-impact labelling is presented, so an agent cannot predict outcomes from the definition 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, including nested arrays for delays, reports, activities, rfis, deliveries, and instructions. The description only obliquely gestures at 'recorded delay rows', 'daily-report delay wording', and 'baseline versus actual dates', leaving most inputs (csv, json, text, file, asOf, scope) unexplained in both schema and description.

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 action: it collects recorded delay rows plus daily-report delay wording and labels impacts inferred from baseline vs actual dates. That is a clear verb+resource, though it doesn't explicitly differentiate itself from siblings like progress-analyze or change-impact.

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 only implied — the tool is for detecting/labelling delay impacts, and 'Liability is not determined' functions as a scope exclusion telling the agent not to expect fault attribution. There is no explicit when-to-use or routing to an alternative tool for related queries.

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