Skip to main content
Glama
Sign In

dipscout

by com.dipscout
OverviewDiscussionsAdmin

Cheaper alternatives

alternativas_mais_baratas
Read-onlyIdempotent

Use this when the user asks for a cheaper option, an alternative, or the same product from another store. Returns cheaper listings that have our own price history: first the same product sold by other stores (relation same_product_other_shop), then products with a similar title in the same category (relation similar_product, not necessarily the same item). Each one has its price difference and its own verdict and certainty. Every product carries pageUrl (the DipScout page with the price chart: the citation link), buyUrl (affiliate link through DipScout, disclosed in monetization; the price is the same with or without it), summary and citation (a self-contained sentence measured from our price history) and verdict (the short answer to "is this a good price?").

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

Input Schema

NameRequiredDescriptionDefault
idiomaNoOptional 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.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.
produtoYesThe AliExpress product URL exactly as the user pasted it (any country or language subdomain: www.aliexpress.com, pt.aliexpress.com, aliexpress.us, aliexpress.ru, m.aliexpress.com, /item/<id>.html, /i/<id>.html, ?productId=<id>), the short link the AliExpress app's Share button copies (a.aliexpress.com/_..., s.click.aliexpress.com/e/_..., even inside the shared sentence), a DipScout product URL, or the numeric product id.

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\" 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"
+]
  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\" 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"
+]
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by explaining result ordering, the two relation types, that similar_product matches are not necessarily the same item, and that each result includes price difference, verdict, certainty, summary, citation, pageUrl, and buyUrl with monetization disclosure. This gives the agent a rich picture of what the tool returns and how to interpret it.

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 usage condition is front-loaded and the rest explains return structure efficiently. It is lengthy, but the length is largely justified because there is no output schema and the tool returns multiple fields with nuanced relations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with no output schema, the description covers the important behavioral and return-value details: ordering, relation types, price comparison, verdicts, citations, and monetization. Together with the input schema, an agent has enough context to call and interpret the tool correctly.

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 75%, so most parameters are already documented in the schema. The description adds no additional detail about produto, mercado, idioma, or limite, relying entirely on the schema for input semantics.

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 action and resource: it returns cheaper listings, first exact product matches from other stores then similar products. The core purpose is clear, but it does not explicitly distinguish itself from siblings like menor_preco or buscar_promocoes.

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 triggering condition: use when the user asks for a cheaper option, an alternative, or the same product from another store. It lacks explicit exclusions or guidance on when a sibling tool would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All dipscout toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources