Skip to main content
Glama

price_to_win

Retrieve buy-box competition data for a Mercado Libre listing to see current price, suggested winning price, visit share, and ranking boosts.

Instructions

Precio para ganar el buy-box / competencia de catálogo de una publicación en Mercado Libre (solo lectura). Devuelve precio actual, precio sugerido para ganar, estado de competencia, participación de visitas y boosts que afectan el ranking.

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": {
      "item_id": "<item_id>"
    },
    "name": "price_to_win"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesID de la publicación en ML (ej: MLA123456789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0-alpha.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral load, and it does disclose the read-only nature and enumerates exactly what is returned, which substitutes for a missing output schema. It does not mention permissions, scoping to the seller's own listings, rate limits, or what happens for listings without catalog competition.

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?

Two compact sentences, front-loaded with the core purpose followed by the return payload; no filler. The parenthetical '(solo lectura)' is the only slightly awkward insertion but it carries real information.

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 one-parameter read tool this is nearly complete: the purpose, the read-only nature and the full return field set are stated, compensating for the absence of an output schema. Only the lack of guidance about how it relates to sibling pricing tools leaves a small gap.

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 100% and the single required parameter item_id already carries an example (MLA123456789), so the schema does the heavy lifting. The description adds no constraint or format detail about item_id beyond what is structured, so the baseline 3 applies.

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 names a specific concept and resource: buy-box/catalog competition for a Mercado Libre listing, plus the data returned (current price, suggested price, competition status, visit share, ranking boosts). That is clearly distinct from siblings like price_history, update_price and search_competitors, though it never names those alternatives explicitly.

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?

Usage is only implied: '(solo lectura)' signals a safe read, and the returned fields imply the scenario of evaluating whether to reprice to win the buy-box. There is no explicit when-to-use/when-not, and no routing guidance versus price_history (historical) or update_price (mutation).

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