Skip to main content
Glama

LEVA building cost estimates

LEVA configurable products

list_products
Read-onlyIdempotent

List LEVA's configurable building products (A-frame, ADU, shed, sauna, barndominium ...) with their configurator type, the number of priced reference designs and whether their options are described.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-openWorld, so the safety profile is covered. The description adds genuinely new context by disclosing what is returned (configurator type, count of priced reference designs, whether options are described). It says nothing about catalog size, ordering, or completeness of the listing.

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?

A single front-loaded sentence with zero filler, and the resource identification comes before the returned-field list. The parenthetical examples add scanability rather than noise.

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 parameters and no output schema, the description carries the burden of describing returns and does so by naming three concrete fields. Minor gap: no indication of result volume or ordering, which matters for a full-catalog listing.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. It correctly conveys that the call is unfiltered and returns the whole catalog view.

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?

Specific verb ('List') plus a well-scoped resource ('LEVA's configurable building products') with concrete examples (A-frame, ADU, shed, sauna, barndominium) and an enumeration of the fields returned. This clearly separates it from get_product (single item) and get_product_prices (pricing), though it does not name 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 Guidelines3/5

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

Usage is only implied: 'configurable building products' signals the catalog-overview scope, and the enumerated output fields hint that this is a survey/discovery step. It never states when to prefer it over get_product or get_product_prices, nor any exclusions.

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