Skip to main content
Glama

BRAINIAC Construction Site Operations

Extract site instructions

construction-site-operations_instruction-extract

Extract dates, issuers, locations, referenced activities, and change flags from supplied site instructions. Price $0.04 USDC. POST /api/v1/construction-site-operations/instruction-extract. 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_instruction-extract"
  }
}

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?

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the price, POST endpoint, and that unpaid calls return 402 and do not run, but it does not state whether the operation is read-only, what permissions are required, or what the response 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?

The description is three compact sentences with the core extraction purpose front-loaded and payment behavior stated efficiently. There is little wasted wording, though the endpoint path could be considered operational detail rather than definitional content.

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?

This is a complex tool with 12 parameters, nested objects, no annotations, and no output schema, yet the description explains neither the input structure nor the return shape. It covers pricing and failure behavior but leaves too much unspecified for reliable 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, and the description does not explain the input modes such as text, csv, json, file, instructions, rfis, reports, or delays. It only identifies the extracted fields, leaving most parameter meaning 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 states a specific verb and resource: extracting dates, issuers, locations, referenced activities, and change flags from supplied site instructions. This is clearly distinguishable from generic reporting or progress tools, though it does not explicitly name a sibling 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?

It implies the tool is for supplied site instructions but gives no guidance on when to choose it over related tools such as daily-report-parse or request-for-information-track. There are no exclusions or prerequisites beyond the payment requirement.

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