Skip to main content
Glama

BRAINIAC Construction Site Operations

Reconcile material deliveries

construction-site-operations_material-delivery-reconcile

Reconcile expected and delivered material records, flagging missing deliveries and short quantities from supplied dates and counts. Price $0.04 USDC. POST /api/v1/construction-site-operations/material-delivery-reconcile. 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_material-delivery-reconcile"
  }
}

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 carries the full burden, and it does disclose genuinely useful behavior: the $0.04 USDC price, the POST endpoint, and that unpaid calls return 402 without executing. However it says nothing about whether the tool persists state, whether it is idempotent, or what the reconciliation output looks like (structured flags vs prose).

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 purpose, then mechanics. No padding, though the payment and endpoint details could be compressed into a single trailing clause.

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 zero schema descriptions and no output schema, the definition is under-specified: an agent cannot tell which of the several input shapes is required, how partial inputs are handled, or what the returned flags look like. It covers billing but not the data contract.

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 deep nested objects (deliveries, rfis, scope, delays, reports, activities, instructions), yet the description only alludes to 'supplied dates and counts'. It does not explain asOf, the quantityExpected/quantityDelivered fields, or what the non-delivery arrays contribute to the reconciliation, so the agent must guess field semantics entirely from property names.

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 ('reconcile expected and delivered material records') plus the two outcomes it produces (missing deliveries, short quantities). It is clearly distinguishable from siblings like delay-event-detect or progress-analyze, though it never explicitly names an alternative.

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 statement of when to use this versus the sibling analysis tools, no prerequisites, and — critically for a tool with five alternative payload shapes (csv, json, text, file, structured deliveries) — no guidance on which input form to supply in which situation.

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