Werop

Buscar prendas

search_products

Read-only

Busca prendas en Werop. Con «query» busca por parecido en texto libre (estilo, ocasión, tejido, color…); sin ella, devuelve las más nuevas con los filtros. Devuelve precio con IVA, tallas disponibles, tienda, enlace y envío al país.

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

Name	Required	Description
`size`	No	Talla tal como la escribe la tienda (S, M, 38, 40…).
`color`	No	Color en español: blanco, negro, gris, rojo, azul, verde, amarillo, rosa, marrón, beige, naranja, morado, dorado, plateado.
`limit`	No
`query`	No	Lo que busca la persona, en su idioma: «vestido de lino verde para una boda de verano».
`gender`	No
`country`	No	País de entrega, código ISO de dos letras. Abierto hoy: ES, FR, DE, IT, PT, LU, IE (por defecto ES). Los demás (ES, FR, DE, IT, NL, BE, AT, PT, LU, IE) responden not_open hasta que se abran.
`category`	No
`max_price_eur`	No	Precio máximo con IVA, en euros.

Output Schema

Name	Required	Description
`note`	No	Aclaraciones sobre precios y envío
`count`	No	Cuántas prendas
`country`	No	País de entrega usado
`products`	No	Cada prenda: productId, name, store {name, username, url}, priceEur (con IVA), previousPriceEur (tachado, o null), currency, category, gender, color, sizesAvailable, soldOut, imageUrl, url, shipping {country, ships, international, priceEur, freeFromEur, deliveryDays {min, max}}

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.6/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 useful behavior beyond that — semantic matching versus recency ordering, and that results carry VAT-inclusive price, available sizes, store, link and country shipping. It says nothing about pagination or what the limit does.

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?

Three tight sentences, front-loaded with the core purpose followed by the query/no-query rule and the result contents. No filler, though the return-fields sentence partly duplicates what the output schema already declares.

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 an 8-parameter, all-optional search tool with an output schema and read-only annotations, the description covers the essential selection logic and result shape. The country open/not_open caveat and the limit ceiling live in the schema, which is acceptable given the coverage.

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 coverage is 63%, and the description adds real meaning for the most important parameter by explaining that «query» triggers fuzzy matching across style/occasion/fabric/color rather than exact keywords. It treats the remaining parameters only collectively as "los filtros", leaving size, color, limit, gender and max_price to the schema.

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?

Uses a concrete verb plus resource ("Busca prendas en Werop") and immediately scopes the tool: free-text similarity when a query is present, newest items when it is not. An agent can distinguish it from get_product (single item) by inference, but no sibling is named explicitly.

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?

Gives a clear decision rule: with «query» it does fuzzy free-text matching over style, occasion, fabric or color; without it, it returns the newest items subject to the filters. It stops short of naming alternatives (get_product, check_availability) for follow-up steps.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Werop tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?