Skip to main content
Glama

compatsy 3D printing

Search products

search_products
Read-onlyIdempotent

Find products by name or by category and spec filters; returns key specs and the best in-stock offer. Example: {"query":"hardened 0.4","category":"nozzle","limit":5}

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
filtersNoNeeds category. Spec field -> exact value, e.g. {"material":"brass"}; an unknown field or value is an error listing the valid ones
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful behavioral context by saying it returns key specs and the best in-stock offer, but it omits ranking details, result ordering, and pagination behavior.

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?

The description is front-loaded with the core purpose and return behavior, followed by a compact example that illustrates all parameter types. There is no unnecessary wording.

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?

For a search tool with four optional parameters, nested filters, and no output schema, the description supplies the search dimensions, return summary, and an example invocation. Remaining gaps such as default limit, matching semantics, and result ordering are minor but nonzero.

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 low at 25%, so the description must compensate. It clarifies that query searches by name, category filters products, and filters are spec-based, and the example shows all four parameters; however, it does not explain limit behavior or the filters-plus-category dependency beyond what the schema already states.

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?

The description uses a specific verb and resource: 'Find products by name or by category and spec filters'. It also states the return content, distinguishing it from a single-product lookup, but it does not explicitly name sibling alternatives such as get_product.

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?

The description explains what can be searched but gives no explicit when-to-use guidance versus siblings like get_product, check_stock, or compare. The example illustrates invocation but does not clarify selection criteria or 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.