Skip to main content
Glama

Detected price drops

quedas_de_preco
Read-onlyIdempotent

Products whose price dropped at least 10% below the TYPICAL price of the last 14 days (median weighted by how long each price lasted — a flash sale only counts for the hours it ran). Requires 7 days of tracking. Each product includes discount.certainty: 'verified' means the drop is proven by the time-weighted median of our readings and MAY be presented as savings; 'none' means there is no discount that can be claimed. The seller's 'was' price on the listing does not support any discount here. Quoting the percentage without the certainty next to it misinforms the reader.

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
idiomaNoOptional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): "en" (default), "de", "pt", "es", "fr", "ko", "it", "pl", "ja", "nl", "he" or "ar". Field names, numbers and currency (USD) are the same in every language.en
limiteNo
mercadoNo"us": only US listings, which ship within the United States only. "global": only listings that ship worldwide. Omit for both. For a shopper outside the US, use "global". Prices are always the ones read for the US.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / idioma / description
      Previous value: -"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\", \"fr\", \"ko\", \"it\" or \"pl\". Field names, numbers and currency (USD) are the same in every language."New value: +"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\", \"fr\", \"ko\", \"it\", \"pl\", \"ja\", \"nl\", \"he\" or \"ar\". Field names, numbers and currency (USD) are the same in every language."
    • changedInput schema / properties / idioma / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "pt",
      -  "es",
      -  "fr",
      -  "ko",
      -  "it",
      -  "pl"
      -]New value: +[
      +  "en",
      +  "de",
      +  "pt",
      +  "es",
      +  "fr",
      +  "ko",
      +  "it",
      +  "pl",
      +  "ja",
      +  "nl",
      +  "he",
      +  "ar"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / idioma / description
      Previous value: -"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\" or \"fr\". Field names, numbers and currency (USD) are the same in every language."New value: +"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\", \"fr\", \"ko\", \"it\" or \"pl\". Field names, numbers and currency (USD) are the same in every language."
    • changedInput schema / properties / idioma / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "pt",
      -  "es",
      -  "fr"
      -]New value: +[
      +  "en",
      +  "de",
      +  "pt",
      +  "es",
      +  "fr",
      +  "ko",
      +  "it",
      +  "pl"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / idioma / description
      Previous value: -"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\" or \"es\". Field names, numbers and currency (USD) are the same in every language."New value: +"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\" or \"fr\". Field names, numbers and currency (USD) are the same in every language."
    • changedInput schema / properties / idioma / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "pt",
      -  "es"
      -]New value: +[
      +  "en",
      +  "de",
      +  "pt",
      +  "es",
      +  "fr"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / idioma / description
      Previous value: -"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\" or \"pt\". Field names, numbers and currency (USD) are the same in every language."New value: +"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\" or \"es\". Field names, numbers and currency (USD) are the same in every language."
    • changedInput schema / properties / idioma / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "pt"
      -]New value: +[
      +  "en",
      +  "de",
      +  "pt",
      +  "es"
      +]
  5. Changed1 schema field changed
    • addedInput schema / properties / idioma
      Added value: +{
      +  "default": "en",
      +  "description": "Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\" or \"pt\". Field names, numbers and currency (USD) are the same in every language.",
      +  "enum": [
      +    "en",
      +    "de",
      +    "pt"
      +  ],
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • addedInput schema / properties / mercado
      Added value: +{
      +  "description": "\"us\": only US listings, which ship within the United States only. \"global\": only listings that ship worldwide. Omit for both. For a shopper outside the US, use \"global\". Prices are always the ones read for the US.",
      +  "enum": [
      +    "us",
      +    "global"
      +  ],
      +  "type": "string"
      +}
  7. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare this as a safe read-only, idempotent, non-destructive operation. The description adds critical behavioral context beyond that: the 90-day history requirement, the median-based methodology, and especially the meaning of discount.verified and the rule that unverified percentages must not be presented as savings.

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?

The description is dense but front-loaded: threshold and methodology first, then tracking requirement, then the critical certainty rule. Every sentence carries operational meaning, including the warning not to quote percentages without the certainty field.

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?

There is no output schema, so the description responsibly explains the key output field discount.verified and the tracking prerequisite. It does not cover pagination, ordering, or how limite/mercado affect results, leaving minor gaps for a 3-parameter tool.

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 67%, with idioma and mercado documented and limite implied by its bounds and default. The description adds no parameter-level meaning beyond the schema, so a baseline score of 3 is appropriate.

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 states a specific resource and condition: products whose price dropped at least 25% below the 90-day median. It is clear what the tool returns, but it does not name or distinguish itself from siblings such as buscar_promocoes or menor_preco.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the detection methodology and data-quality caveat, but it gives no explicit guidance on when to use this tool versus the sibling price tools. An agent must infer applicability from the name and description alone.

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