Skip to main content
Glama

LEVA building cost estimates

Search LEVA's material catalogue

search_items
Read-onlyIdempotent

Find items of LEVA's material catalogue (doors, windows, lumber, insulation, fasteners, membranes ...) by words, e.g. 'interior door', 'exterior door 36', 'window'. Gives ids for get_item_prices.

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": {
      "q": "<q>"
    },
    "name": "search_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYeswords to look for
limitNoat most this many (1-50, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and scope profile is fully covered. The description adds only the keyword-search nature and the hand-off to get_item_prices; it says nothing about matching behavior (substring vs fuzzy), ranking, or empty-result handling for a search tool where that matters.

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: purpose first, category enumeration next, examples after, and the downstream chaining note last. The parenthetical item list is somewhat long but functions as routing vocabulary, so nearly every word earns its place.

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 correctly compensates by saying it returns ids for get_item_prices, and it covers both parameters plus domain vocabulary. What it omits is result-shape detail (what fields accompany the ids) and matching/pagination behavior, which keeps it below a 5 for a search tool.

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%, so 'q' and 'limit' (1-50, default 20) are already documented, and the baseline is 3. The examples of query phrasing ('exterior door 36') add modest real value about what the search string should look like, but do not explain matching semantics.

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

Purpose5/5

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

Uses a specific verb ('Find items') against a named resource ('LEVA's material catalogue'), enumerates the item categories covered, and gives concrete query examples. It also distinguishes itself from retrieval siblings by stating it returns ids intended for get_item_prices rather than prices themselves.

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

Usage Guidelines4/5

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

The example queries ('interior door', 'exterior door 36', 'window') show clearly what kind of keyword input this tool expects, and the closing clause 'Gives ids for get_item_prices' tells the agent this is the entry point before pricing. There is no explicit statement of when NOT to use it (e.g. exact-id lookup via get_product), so it falls short of a 5.

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