Skip to main content
Glama

Preço e histórico de um produto no Pechim

preco_de_produto
Read-onlyIdempotent

Preço atual em cada loja de um produto do Pechim, com link direto para compra, hora da verificação e resumo do histórico ("Esse preço está bom?", "Menor preço em N dias", etc.). Use após buscar_produto para ver o detalhe completo de um produto. Aceita o endereço da página do Pechim (https://pechim.com.br/produto/...) ou só o slug.

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": {
      "url_ou_slug": "<url_ou_slug>"
    },
    "name": "preco_de_produto"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_ou_slugYesEndereço da página do produto no Pechim ou o slug (ex.: "smart-tv-55-4k-samsung").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description goes beyond them by describing what the call returns (per-store prices, direct purchase link, verification timestamp, historical summary verdicts) — valuable since there is no output schema. It says nothing about freshness guarantees, rate limits, or behavior for a slug that no longer exists.

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?

Three front-loaded sentences that each carry information: what is returned, when to call it, and what input it accepts. Minor redundancy where the accepted-input sentence partly restates the schema's parameter description.

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 full annotation coverage, the definition supplies purpose, return contents, input flexibility, and ordering relative to buscar_produto. The only remaining gap is failure/edge behavior (invalid or expired slug), which is modest for a lookup tool.

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 100% with a single required parameter, so the baseline is 3. The description adds a concrete accepted form not present in the schema — the full 'https://pechim.com.br/produto/...' URL pattern — alongside the slug, clarifying that either input shape is valid.

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 resource (current price per store for a Pechim product) plus the payload contents: purchase link, verification time, and history summary. It also distinguishes itself from the sibling by framing itself as the detail view that follows buscar_produto, so an agent can tell the two apart without opening either 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?

Explicitly sequences usage: 'Use após buscar_produto para ver o detalhe completo de um produto', which gives a clear trigger condition and names the alternative. It stops short of stating when not to call it (e.g. when the user only wants a list of matches), so it is not a full when/when-not statement.

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