favoritos_quitarQuita una subasta de tus favoritos. Requiere cuenta (scope favoritos:write).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Identificador público de la subasta (10 caracteres) |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| cta | No | ||
| favorito | Yes | ||
| disclosure | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Las anotaciones ya indican destructiveHint=true y readOnlyHint=false, y la descripción no contradice eso. Añade valor al especificar el requisito de cuenta y el scope 'favoritos:write', que no están en las anotaciones ni en el esquema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
La descripción es una sola oración directa y sin relleno. Comunica la acción y el requisito principal de forma eficiente, con la información clave al frente.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Para una herramienta con un solo parámetro, esquema completo, anotaciones de seguridad y esquema de salida, la descripción es suficiente. No faltan elementos críticos para que un agente seleccione y use correctamente la herramienta.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
El esquema cubre el 100% del parámetro 'id', incluyendo formato y descripción. La descripción no agrega detalles adicionales sobre el parámetro, solo confirma que se refiere a una subasta, por lo que se mantiene en el nivel base.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
La descripción usa un verbo específico ('Quita') y un recurso claro ('una subasta de tus favoritos'), lo que identifica exactamente la operación. Se distingue fácilmente de las herramientas hermanas favoritos_anadir y favoritos_listar por el verbo y el contexto.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
La descripción deja claro que sirve para quitar una subasta de favoritos, por lo que el uso es deducible. Sin embargo, no menciona explícitamente cuándo no usarla ni señala alternativas como favoritos_anadir o favoritos_listar; solo indica que requiere cuenta.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are grouped into recognizable clusters (alertas, checkout, favoritos, notas), but several retrieval/report tools overlap: `fetch` and `subasta` both expose an auction record, and `analisis_subasta` and `informe` both provide analysis. The descriptions give enough distinguishing detail, but an agent must read closely to avoid misselection.
Naming mixes Spanish and English, and mixes conventions: `alertas_crear` and `buscar_subastas` are Spanish compound names, `create_checkout`/`cancel_checkout` are English verb_noun, while `fetch`, `search`, `subasta` and `informe` are bare words. There is internal consistency within clusters, but no coherent pattern across the full toolset.
32 tools is a large, heavy surface for one MCP server, exceeding the 25+ threshold where consolidation is usually needed. Many tools earn their place given the broad platform, but the multiple search/retrieval variants and five checkout lifecycle tools could be streamlined.
The server covers the core domain thoroughly: auction search/retrieval, viability reports, alerts, favorites, registry notes, market statistics, plans/account, and UCP checkout all have lifecycle coverage. Minor gaps exist, such as no explicit report-purchase history and some payment steps being delegated to a browser, but agents can complete most workflows.