Skip to main content
Glama

LEVA building cost estimates

One LEVA product

get_product
Read-onlyIdempotent

One LEVA product by its handle (e.g. a-frames, adu): description, plan price, configuration options (sizes, roof, foundation ...) and LEVA's reference designs with their itemized budgets (materials, execution/labour, hours, $/sq ft; USD 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesthe product handle, from list_products

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond that: the budgets are 'USD estimates, not quotes', and hours and $/sq ft are derived figures, which warns the agent not to present them as firm pricing. It does not mention caching or whether the reference designs are always present.

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 front-loaded sentence: the resource and key come first, then the returned fields in a compact enumerated list. It is dense but every clause identifies actual return content, with no filler or repetition of the title.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so at a useful level of detail (configuration options, itemized budgets with materials, labour, hours, $/sq ft). The main residual gap is error behavior for an unknown or stale handle, which is not addressed.

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

Parameters4/5

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

With a single parameter at 100% schema coverage, the schema already explains that handle comes from list_products. The description adds concrete example values ('a-frames, adu'), which helps the agent recognize the handle format and generate valid inputs without a prior lookup.

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 verb+resource ('One LEVA product by its handle') and enumerates the payload: description, plan price, configuration options, and reference designs with itemized budgets. It is clear what is returned, but it never names the nearest sibling (get_product_prices, get_item_prices) or states how this differs from fetching prices alone.

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

Usage Guidelines3/5

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

The only routing hint is indirect: 'handle, from list_products' tells the agent where the key comes from, and the mention of included prices hints this is the full-detail call rather than a price-only one. There is no explicit when-to-use, when-not-to-use, or alternative named, so selection against get_product_prices is left to inference.

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