Skip to main content
Glama

AstraNL Coordination Protocol

estimate_cost

Read-onlyIdempotent

Instant planning cost figure in EUR for one job category in the Netherlands (not a quote; answers in under 2 s). labor_cost = labor_hours x labor_rate x location_mult, always. The rate comes from AstraNL's S_PRICEBASE (CAO wage with employer cost, overhead and profit) or its labour cost canon; hours from CBS-derived norms where AstraNL has one, otherwise a planning factor labelled ASSUMPTION; location_mult is 1.0 with its basis (no sourced regional factor for renovation labour). Each material line says price_source live_read (store, read_at, product link) or indicative (basis and date). No robot price or savings is given without evidence. Sources are in estimate.labour and estimate.materials. This is a planning figure, not a reviewed estimate of a real job. Read-only, free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
area_m2NoSurface area or working volume in square meters. Optional but improves accuracy. For non-area tasks (e.g. plumbing repair) pass 0 or omit.
categoryYesService category. Same enum as create_task.
locationNoCity in the Netherlands. Pricing varies by region (Amsterdam tends to be highest). Optional — omitting uses national median.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description still adds substantial behavior: latency budget, the deterministic labor_cost formula, source provenance (S_PRICEBASE, CAO, CBS norms), explicit ASSUMPTION labelling, and a stated refusal to emit robot price or savings without evidence. That is exactly the kind of epistemic-honesty context annotations cannot convey.

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 purpose and the not-a-quote caveat, and the formula sentence anchors the rest. It is somewhat dense and the provenance detail (S_PRICEBASE, CBS norms, live_read vs indicative) runs long, but each clause carries real information rather than restating the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description takes on the burden of explaining returns and does so: it names the estimate.labour and estimate.materials sections, the price_source distinction (live_read with store/read_at/link vs indicative with basis and date), and the ASSUMPTION marker. Nothing an agent needs in order to call this and interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter meaning is largely carried by the schema. The description adds a note that location_mult is 1.0 because there is no sourced regional factor for renovation labour, which is useful but sits in tension with the schema's claim that 'Pricing varies by region (Amsterdam tends to be highest)' — an agent cannot tell whether location matters or not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Instant planning cost figure in EUR for one job category in the Netherlands') and immediately delimits it against adjacent artifacts ('not a quote', 'not a reviewed estimate of a real job'). An agent can tell this apart from an evidence-gathering or offer-finding sibling without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use: instant (<2 s) planning-grade figures, explicitly not a reviewed estimate and not binding. It does not name a sibling to route to when a real quote or grounded evidence is needed, so the alternative-selection advice is implied rather than explicit.

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