Skip to main content
Glama

LEVA building cost estimates

A LEVA product's material prices over time

get_product_prices
Read-onlyIdempotent

What the materials of a LEVA product's reference design (or default design) cost at the cheapest store offers, day by day, in 19 countries (local currency and USD), with coverage and the change over time. 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": {
      "handle": "<handle>"
    },
    "name": "get_product_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesthe product handle, from list_products (e.g. adu, barndominium, sauna-1)

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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: day-by-day granularity, 19-country coverage, dual currency, inclusion of coverage and change over time, and the important caveat that values are estimates rather than quotes.

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?

It is a single dense sentence that is front-loaded with the core subject and progressively narrows to the caveat. Every clause carries information, though the parenthetical '(or default design)' and the semicolon-joined disclaimer make it slightly hard to parse at a glance.

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?

With no output schema, the description does the work of characterizing the return: per-day material cost series, cheapest offers, country and currency dimensions, plus coverage and change over time. It omits response shape details (units, missing-data behavior, date-range control), but for a one-parameter read tool it is close to sufficient.

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?

There is a single parameter with 100% schema description coverage, including the source tool (list_products) and examples, so the schema carries the semantic load. The description adds nothing about the handle — not its format, validity, or what happens for an unknown handle — so the baseline of 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?

The description names a specific resource (materials of a LEVA product's reference or default design) and what is returned about them (cheapest store offers, day by day, in 19 countries, local and USD). It implicitly separates itself from get_project_prices and get_item_prices by scoping to a product's material bill of materials, but it never names a sibling 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?

There is no explicit when-to-use or when-not guidance, and no routing to get_item_prices or get_project_prices for item- or project-level pricing. The only scoping signal is the closing clause 'Materials only; estimates, not quotes', which tells the agent what the data is, not when to choose this tool over its neighbors.

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