Skip to main content
Glama

compare_products

Compara hasta 5 productos lado a lado en precio MXN IVA incluido, stock en México y elegibilidad de envío gratis.

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": {
      "producto_ids": "<producto_ids>"
    },
    "name": "compare_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
producto_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the compared dimensions: MXN price with IVA included, stock in Mexico, and free-shipping eligibility. It does not state that the tool is read-only with no side effects, nor what happens with invalid or duplicate IDs, leaving some behavioral gaps.

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 front-loaded sentence that names the action, the limit, and the exact comparison dimensions with zero filler. Every element earns its place.

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 simple one-parameter read tool with no output schema, the description adequately conveys what the comparison returns (price, stock, shipping eligibility). Minor omissions are error behavior and the ID format, but an agent has enough to call it correctly.

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 0% for the single producto_ids array, so the description must compensate. It adds the meaningful constraint of 'hasta 5 productos' but never explains the expected ID format (e.g., SKU vs numeric ID) or whether order matters, so compensation is only partial.

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 ('Compara') and resource ('productos') plus scope ('lado a lado', 'hasta 5'), which clearly separates it from search_products and get_product_details. It doesn't explicitly name a sibling to contrast against, keeping it short of a 5.

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?

The cap of 5 products and the side-by-side framing imply when the tool fits, but there is no explicit guidance on when to use it instead of get_product_details for a single item or search_products for discovery. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources