Skip to main content
Glama

BRAINIAC Construction Site Operations

Compare construction change impact

construction-site-operations_change-impact

Compare change instructions with supplied scope and programme dates. Linked schedule impact is labeled inferred and is not a liability finding. Price $0.05 USDC. POST /api/v1/construction-site-operations/change-impact. 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_change-impact"
  }
}

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

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

With no annotations, the description does real work: it discloses that linked schedule impact is labeled inferred and is not a liability finding, that the call is paid ($0.05 USDC), that it is a POST to a specific endpoint, and that unpaid calls return 402 without executing. That payment gating and the inference caveat are behavior an agent could not get from schema or annotations. It does not describe the response shape or partial-input behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences: purpose first, then the interpretation caveat, then cost and endpoint, then failure behavior. Every sentence carries distinct information and nothing is repeated from the title or schema.

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, zero-annotation tool with no output schema, the description leaves most of the input surface unexplained and gives no sense of which inputs are needed for a meaningful comparison or what the result contains. The commercial and caveat details are well covered, but the operational picture is thin.

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 top-level parameters, many with nested objects, so the description must compensate and largely does not. It alludes to instructions, scope, and programme dates (likely activities), but says nothing about csv, file, json, text, asOf, rfis, delays, reports, or deliveries, nor how the free-text versus file versus structured variants interact.

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 change instructions against supplied scope and programme dates. The subject matter (change instructions / schedule impact) distinguishes it from siblings like delay-event-detect or progress-analyze, though it never names those alternatives directly.

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 required inputs (change instructions plus scope and programme dates), so an agent can infer what to supply. However, there is no explicit when-to-use versus when-not guidance, and no statement of prerequisites or what happens if only some inputs are provided.

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