Skip to main content
Glama

historico_preco

Read-only

Mostra o histórico REAL de preços que a Lupa registrou para um produto (menor preço visto por dia), para dizer se o preço de hoje está bom ou se já esteve mais barato. Cobre os ~40 mil produtos das lojas oficiais parceiras (Nike, adidas, Mizuno, Olympikus, KaBuM!, Posthaus), gravados TODO DIA desde 16/11/2026, e os produtos já pesquisados na Lupa; o histórico cresce a cada dia.

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": "historico_preco"
  }
}

Input Schema

NameRequiredDescriptionDefault
produtoYesO produto, em português. Ex.: "air fryer 4l".

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=true and openWorldHint=true, so the safety profile is covered. The description does add valuable non-obvious behavior: coverage is limited to ~40k products from named partner stores plus previously searched products, recorded daily since a fixed date. It does not say what happens for an unregistered product or how sparse/missing history is reported.

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

Conciseness3/5

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

The purpose is front-loaded and the store/coverage sentence is informative, but the text is padded with emphatic capitalization (REAL, TODO DIA) and the store list plus the closing 'o histórico cresce a cada dia' partially repeats the daily-recording claim already made.

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-only lookup with no output schema, the description covers scope, data source, and recency well enough to call correctly. It leaves the shape of the returned history (per-day entries, ranges, empty results) unstated, which would help given there is no output schema.

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 parameter already includes a Portuguese example, so the schema does the work. The description only says 'para um produto' and adds no format, normalization, or matching-behavior detail beyond the 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 and resource: shows the real registered price history for a product, specifically the lowest price seen per day. The purpose is clearly separable from a current-price search or a list comparison, but no sibling tool is named, so the differentiation is left implicit.

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?

Gives a clear usage context: use it to judge whether today's price is good or whether the item has been cheaper before. There is no explicit when-not-to-use guidance or named alternative (e.g. a live-price search tool) for cases where no history exists.

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