Skip to main content
Glama

buscar_preco

Read-only

Procura um produto em várias lojas do Brasil (Shopee, AliExpress, Mercado Livre, lojas oficiais Adidas, Nike, Mizuno, Olympikus, KaBuM! e Posthaus, Amazon, Magalu, lojas parceiras e mais de 130 lojas via Google Shopping) e devolve as ofertas do mais barato para o mais caro, com o "preço justo" (mediana do mercado) quando há preços suficientes do mesmo produto. Use para "qual o menor preço de X", "onde comprar X mais barato", "X está caro?".

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": {
      "produto": "<produto>"
    },
    "name": "buscar_preco"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoQuantas ofertas devolver (padrão 10, máximo 25).
produtoYesO que procurar, em português, como uma pessoa diria. Ex.: "air fryer 4 litros", "fone bluetooth jbl", "liquidificador mondial l-99".
preco_maximoNoOpcional: não mostrar ofertas acima deste valor em reais.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuine behavior beyond that: result ordering (ascending price), the conditional inclusion of a median "preço justo" only when enough prices exist for the same product, and the breadth of sources searched. It stops short of stating what happens when nothing is found or how results are ranked across stores.

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?

The verb and scope are front-loaded, and the second sentence efficiently delivers trigger examples. The long parenthetical store enumeration is somewhat heavy, but it earns its place by communicating coverage, so the text stays purposeful.

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?

With no output schema, the description carries the burden of explaining returns, and it does so (sorted offers plus optional fair-price median). For a three-parameter read-only search tool this is nearly complete; only edge cases like zero results or how the median is computed are unaddressed.

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 every parameter (produto, limite, preco_maximo) is documented in the schema itself, so the baseline is 3. The description adds no extra meaning about parameter interaction — e.g., how preco_maximo affects the median calculation — so it does not exceed the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Procura um produto") and scope (multiple Brazilian stores, named sources plus 130+ via Google Shopping), and describes the output shape (offers sorted cheapest to most expensive, plus a market-median "preço justo"). An agent can distinguish this from price-history or list-comparison siblings without opening any schema.

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?

Provides concrete trigger phrases ("qual o menor preço de X", "onde comprar X mais barato", "X está caro?") that map cleanly to the tool's behavior, giving strong positive guidance. It does not, however, say when NOT to use it or point to the siblings (historico_preco, comparar_lista, ofertas_do_dia), leaving that 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