Skip to main content
Glama

BRAINIAC Construction Site Operations

Analyze site progress

construction-site-operations_progress-analyze

Compare supplied baseline and actual activity dates to identify schedule deviations. Inferred impact is labeled and is not an entitlement determination. Price $0.05 USDC. POST /api/v1/construction-site-operations/progress-analyze. 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_progress-analyze"
  }
}

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.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses the $0.05 cost, the 402 failure mode for unpaid calls, and a caveat that inferred impact is labeled and is not an entitlement determination. What it omits is behavior around the many input modes (csv vs. json vs. text vs. file) and what the returned analysis contains.

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 compact sentences, front-loaded with the purpose before the caveat, price, endpoint, and payment failure. The endpoint path largely repeats the tool name, a minor redundancy, but nothing is padded.

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 tool with nested records, no annotations, and no output schema, the description should at minimum explain which input channel to supply and what the analysis returns. The pricing and non-entitlement caveats are useful, but the input contract is essentially undocumented, which is a significant gap before invocation.

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, several with nested object arrays (activities, delays, rfis, reports, scope, deliveries, instructions). The description adds only an implicit hint about baseline/actual date fields and says nothing about how csv, json, text, and file inputs relate or what asOf controls, leaving nearly all parameter meaning to the bare schema.

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: compare baseline vs. actual activity dates to identify schedule deviations. That is concrete enough to distinguish it from siblings like change-impact or delay-event-detect, though it never names those alternatives 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 comparison framing implies when the tool applies, and the payment clause ('Unpaid calls return 402 and do not run') is a genuine usage prerequisite. However, there is no explicit when-to-use guidance and no routing to sibling analysis tools, so the agent must infer fit from the purpose sentence alone.

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