Werop

Comprobar una talla

check_availability

Read-only

Comprueba, justo antes de preparar la compra, si una prenda está disponible en una talla para un país de entrega: si queda stock (y cuántas unidades si son pocas), el precio actual con IVA y el envío. Si la prenda no tiene tallas, deja «size» vacío.

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": {
      "product_id": "<product_id>"
    },
    "name": "check_availability"
  }
}

Input Schema

Name	Required	Description
`size`	No	La talla tal como la escribe la tienda (S, M, 38…).
`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.
`product_id`	Yes	El productId de search_products.

Output Schema

Name	Required	Description
`url`	No	La ficha en Werop
`name`	No
`size`	No	La talla comprobada
`priceEur`	No	Precio actual con IVA
`shipping`	No	Envío al país
`available`	No	Si se puede comprar ahora en esa talla
`productId`	No
`unitsLeft`	No	Unidades que quedan si son pocas (3 o menos); si no, null
`sizesAvailable`	No	Las tallas con stock, por si la pedida no lo tiene

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.3/5.0

Behavior4/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 behavioral context: it discloses the returned signals (stock, low-unit counts, price with VAT, shipping) and the empty-size rule. It does not define what 'pocas' units means, leaving one behavioral threshold vague.

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 that leads with the action and timing, then the outputs. It is dense with parenthetical detail but every clause carries relevant information; minor tightening could improve readability.

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 an output schema present and full parameter coverage, the description need not explain return structures. It covers purpose, timing, and key edge behavior, though it leaves the low-stock threshold undefined and does not mention error or not_open handling beyond what the schema documents.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by specifying that 'size' should be left empty when the garment has no sizes, which is meaningful invocation guidance not present in the schema.

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?

States a specific verb and resource: checks whether a garment is available in a given size for a delivery country, and enumerates what is returned (stock, unit count when low, current price with VAT, shipping). This is clearly distinguishable from siblings such as get_product or search_products.

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 an explicit timing cue, 'justo antes de preparar la compra', which tells the agent when this tool belongs in a flow. It does not name alternatives or state when not to use it, so it falls short of full when/when-not guidance.

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?