Skip to main content
Glama

LEVA building cost estimates

A LEVA reference design's material prices over time

get_project_prices
Read-onlyIdempotent

One LEVA reference design's own bill of quantities priced at the cheapest store offers, day by day, in every country (USD), with coverage. Materials only; estimates, not quotes.

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": {
      "id": "<id>"
    },
    "name": "get_project_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe ?p= id of a reference design (see get_product)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered; the description adds genuinely new behavioral context: prices are the cheapest store offers, tracked daily across all countries, in USD, and reported 'with coverage'. The caveat 'Materials only; estimates, not quotes' tells the agent how to treat the numbers, which 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?

One dense front-loaded sentence covering scope and resolution, plus a short caveat clause. No filler, though the phrasing is compressed enough that 'coverage' and 'day by day' take a moment to parse.

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

Completeness4/5

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

For a read-only single-parameter tool with no output schema, the description covers data source, granularity, currency, geography, and a material accuracy caveat. It leaves the return shape (per-material rows vs. aggregates) unstated, but nothing needed to decide to call it 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 description coverage is 100% and the single 'id' parameter is documented in-schema as the ?p= reference design id pointing to get_product. The description adds no further parameter semantics beyond scope, so baseline 3 applies.

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 resource and scope: one LEVA reference design's own bill of quantities, priced at cheapest store offers, day by day, per country in USD. An agent can distinguish this from get_item_prices/get_product_prices by the 'reference design's own bill of quantities' framing, though it never names an alternative explicitly.

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?

No when-to-use or when-not-to-use guidance, and no named alternative (e.g. get_item_prices vs get_product_prices vs this). The only implicit routing signal is the required 'id' described as 'the ?p= id of a reference design (see get_product)', which points at which tool supplies the id rather than when to call this one.

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