Skip to main content
Glama
Mercado Libre MCP

Mercado Libre MCP

by fedeclavero

meli_guia_imagen

Read-onlyIdempotent

Fetches and displays an image or formula from a Mercado Libre guide by number; use the section lookup to find the correct guide number.

Instructions

Muestra una imagen o fórmula de la guía por su número; consúltalo en meli_guia_seccion.

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": {
      "numero": "<numero>"
    },
    "name": "meli_guia_imagen"
  }
}

Input Schema

NameRequiredDescriptionDefault
numeroYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds that the result is an image or formula, which is useful, but says nothing about return format, size, or error behavior. Given the annotation coverage, a 3 is appropriate.

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

Conciseness5/5

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

A single compact sentence with no wasted words; the retrieval action and number dependency are front-loaded.

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 single-parameter read-only lookup with no output schema, the description supplies the missing parameter meaning and the source for the número. It does not describe output details, but those are not strictly necessary here.

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 0%, so the description must carry the burden. It explains that 'numero' is the guide number and points to meli_guia_seccion for how to find it, which is meaningful semantics beyond the bare integer 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?

States a specific verb ('Muestra') and resource ('una imagen o fórmula de la guía') retrieved by número. It also implicitly distinguishes itself from the section-lookup sibling by pointing to it. Lacks a title, but the description itself is clear.

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?

Explicitly tells the agent where to obtain the required número ('consúltalo en meli_guia_seccion'), which is a useful routing instruction. It does not explain when to use this instead of meli_guia_indice or meli_guia_seccion, but the dependency is clear.

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