Skip to main content
Glama

Search robot catalog

search_robot_catalog
Read-onlyIdempotent

Search Valumech's read-only robot catalog by words, category, market status, or a maximum approximate USD price. At least one filter is required.

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": "search_robot_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return, from 1 through 5.
queryNoRobot, maker, capability, body form, or use-case words.
statusNoCommercial status recorded by Valumech.
categoryNoValumech's semantic robot category.
maxPriceUsdNoMaximum new price normalized approximately to USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotent, openWorld false). The description restates 'read-only' and adds the at-least-one-filter requirement, but provides no further behavioral details like rate limits, sorting, or how filters combine.

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

Conciseness5/5

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

Two tightly written sentences. The search scope is front-loaded, and the required-filter constraint follows immediately with no wasted words.

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?

Given a 5-parameter tool with full schema coverage and annotations covering safety, the description is nearly complete. It omits how multiple filters combine (AND/OR) and result ordering, which are minor gaps for a search tool with no output schema.

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?

Schema description coverage is 100%, so the baseline would be 3. The description adds a meaningful semantic constraint—that at least one filter must be supplied—and maps the filter parameters (words, category, status, max price) to their fields, lifting it above baseline.

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 ('Search') and resource ('Valumech's read-only robot catalog'), and lists the filter dimensions. It does not explicitly distinguish itself from siblings like get_robot_price or compare_robots, but the purpose is clear enough to select it.

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?

Adds a prerequisite not in the schema ('At least one filter is required'), which is useful. However, it gives no explicit when-to-use or when-not guidance relative to alternatives, leaving the agent to infer context.

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