Skip to main content
Glama

LEVA building cost estimates

One catalogue item's cheapest price over time

get_item_prices
Read-onlyIdempotent

The cheapest offer found for one LEVA catalogue item, per unit, in each country's currency and USD, over time; checked against LEVA's own price and the other countries (pack prices replaced).

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_item_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe item id from search_items
marketNooptional two-letter country code, e.g. US

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world, non-destructive), and the description adds genuinely non-obvious data semantics: values are normalized per unit, returned in both local currency and USD, and pack prices are replaced so comparisons are apples-to-apples. It stops short of disclosing time-range defaults, granularity, or result volume.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense sentence that front-loads the resource, but the clause chain ('checked against... the other countries (pack prices replaced)') is grammatically loose and takes effort to parse. Nothing is strictly redundant, yet the parenthetical placement obscures an important behavioral detail.

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

Completeness3/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 must carry more of the return-shape burden, and 'over time' is left undefined — no mention of the time window, sampling frequency, or whether results are a series or a per-country list. For a price-history tool that is a meaningful gap, though the currency and normalization details are covered.

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 both parameters are already documented, and the baseline applies. The description does add meaning: 'per unit' clarifies how figures are normalized, and 'in each country's currency' implies that omitting market yields all countries rather than a single default.

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

Purpose3/5

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

The description identifies a specific resource (one LEVA catalogue item's cheapest per-unit offer over time) but is written as a noun phrase with no verb, so the action is only inferred from the tool name. It also never distinguishes this from siblings like get_product_prices, which by name sounds very close.

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 call this versus get_product_prices or get_project_prices, and no prerequisite context beyond the schema's note that id comes from search_items. The 'checked against LEVA's own price' clause describes output content, not invocation guidance.

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