Skip to main content
Glama

search_products

Read-only

Busca productos públicos por texto o filtros. Prioriza referencias exactas de producto, Tilda o combinación y usa disponibilidad sincronizada.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
cursorNo
filtersNo

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / filters / properties / minimum_cut_mm
      Added value: +{
      +  "description": "Exact product minimum cut in millimetres (25 cm = 250). Products without a numeric minimum cut do not match.",
      +  "maximum": 4294967295,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / properties
      Added value: +{
      +  "items": {
      +    "items": {
      +      "properties": {
      +        "minimum_cut": {
      +          "properties": {
      +            "label": {
      +              "type": "string"
      +            },
      +            "mm": {
      +              "type": [
      +                "integer",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": [
      +            "object",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "minimum_cut"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  }
      +}
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds two real behavioral facts beyond that: results are restricted to public products, and availability data is synchronized. However, 'Tilda o combinación' is unexplained jargon and nothing is said about result ordering, result caps, or pagination despite cursor and limit parameters.

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

Conciseness3/5

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

Two tight, front-loaded sentences with no filler, so length is fine. The problem is lexical rather than structural: 'Tilda' and 'combinación' are opaque to an agent and consume the space that could have carried useful signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values needn't be described. But for a search tool with a nested filter object at 0% schema coverage, the definition leaves pagination, filter combination semantics, and units unexplained, which is not enough to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 0% across 4 top-level parameters and a nested filters object with nine undocumented fields, so the description carries the burden and largely fails. It only gestures at query vs filters; it never explains limit/cursor paging, what width_mm or minimum_cut_mm mean (only the latter has a schema description), or how multiple filter arrays combine.

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 and resource ('Busca productos públicos') plus the two input modes ('por texto o filtros'), which lets an agent distinguish it from a single-item lookup like get_product. It does not explicitly name a sibling or contrast its behavior, so it stops short of a 5.

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 'texto o filtros' phrasing implies the two valid invocation modes, matching the anyOf in the schema, and 'Prioriza referencias exactas' hints at query strategy. It never says when to prefer this over get_product or get_product_availability, and gives no exclusions or prerequisites.

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