Skip to main content
Glama

Quedas de preço detectadas

quedas_de_preco
Read-onlyIdempotent

Produtos cujo preço caiu pelo menos 10% contra o valor TÍPICO dos últimos 30 dias (mediana ponderada pelo tempo que cada preço vigorou — promoção-relâmpago pesa só as horas que durou), ou que atingiram o menor preço já registrado. Exige 7 dias de acompanhamento. Cada produto traz discount.certainty: 'verified' significa que a queda está provada pela mediana ponderada pelo tempo das nossas leituras e PODE ser apresentada como economia; 'none' significa que não há desconto que se possa afirmar. O preço 'de' que o vendedor escreve no anúncio não sustenta desconto nenhum aqui. Citar o percentual sem o certainty ao lado desinforma o leitor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quedas_de_preco"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description explains the time-weighted median methodology, the 7-day tracking requirement, the meaning of discount.certainty values, and the important caveat that the seller's 'from' price does not justify a discount. It also warns that citing a percentage without certainty misleads the reader, which is substantial behavioral context.

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 description is front-loaded with the core definition before adding methodology and certainty caveats. It is somewhat long and repeats the certainty warning, but nearly every sentence adds useful domain context rather than filler.

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?

Given the tool's complexity and lack of an output schema, the description does a good job explaining the discount.certainty field and the conditions for a verified drop. The main gap is the unexplained limite parameter, but the core selection and interpretation guidance is otherwise complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, limite, is not mentioned in the description at all. Schema description coverage is 0%, so the description does not compensate for the missing parameter semantics; the schema's name, default, and min/max constraints are the only guidance available.

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?

The description clearly states a specific resource and criteria: products whose price fell at least 10% versus the time-weighted median of the last 30 days, or reached their lowest recorded price. This is far more specific than a tautology, but it does not explicitly differentiate this tool from siblings like buscar_promocoes or historico_de_preco.

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 the detection criteria and the requirement of 7 days of tracking, but there is no explicit when-to-use/when-not-to-use guidance or direct routing to alternatives such as buscar_promocoes or historico_de_preco. An agent can infer the tool's purpose, but must decide on its own when this is preferable to the sibling tools.

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