Skip to main content
Glama

Compara MEI: card machines, websites, e-commerce, CRM and ERP for Brazilian small businesses

Comparar produtos lado a lado

comparar_produtos
Read-onlyIdempotent

Compara de 2 a 4 produtos (ex.: PagBank vs InfinitePay, Nuvemshop vs Shopify) em preço, taxas e recursos.

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": {
      "ids": "<ids>"
    },
    "name": "comparar_produtos"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds only the comparison dimensions and the 2-4 limit, without noting return shape or how missing data is handled.

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 with the verb, scope, and examples in order of importance. No filler or redundancy.

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 read-only tool with one parameter and no output schema, the description covers what is compared and the cardinality constraint. Adding a hint about the comparison result structure would complete it, but nothing essential is missing.

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%, so the single "ids" parameter is undocumented in the schema. The description partially compensates by stating 2 to 4 products, matching minItems/maxItems, but never clarifies that the ids are product identifiers or their expected format.

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?

Specific verb ("Compara") plus resource ("produtos") with concrete scope (2 to 4) and examples of comparison dimensions (preço, taxas, recursos). It differentiates from a lookup like ficha_produto, but doesn't explicitly name the sibling alternatives it should be chosen over.

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 implied by "comparar" and the 2-4 product bound, so an agent can infer this is for side-by-side evaluation. However, there is no explicit statement of when to prefer this over buscar_produtos, alternativas, or ficha_produto, leaving routing to inference.

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