Skip to main content
Glama
Sign In

dipscout

by com.dipscout
OverviewDiscussionsAdmin

Lowest price in N days

menor_preco
Read-onlyIdempotent

Use this when the user asks for the lowest (or cheapest) price of an AliExpress product over a period: "lowest price in the last 30 days", "has it been cheaper?", "is this the lowest price ever?". Returns the lowest price in effect during the window, when it held, and how far today's price is from it. If our tracking began after the window opened, the answer says how many of the requested days it covers; it never claims a low beyond our own history. 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": "menor_preco"
  }
}

Input Schema

NameRequiredDescriptionDefault
diasNoWindow in days, counted back from now.
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
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

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses a real behavioral trait: it reports how much of the requested window its own history covers and never claims a low beyond its data. It also flags affiliate monetization of buyUrl and states the price is identical with or without it, which is useful trust 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?

Front-loads the trigger condition, then the return-shape explanation, with little filler. The final sentence enumerating pageUrl/buyUrl/summary/citation/verdict is long but carries information the agent cannot get elsewhere, since there is no output schema.

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?

With no output schema, the description usefully enumerates the returned fields (pageUrl, buyUrl, summary, citation, verdict) and the history-coverage caveat, making it complete enough to call and interpret. The only gap is not stating the sibling boundaries.

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%, so dias, idioma and produto are already well documented in the schema. The description adds only indirect meaning (window semantics, history coverage) and nothing new about accepted URL forms or language behavior, so the baseline 3 applies.

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+resource: returns the lowest price of an AliExpress product over a window, plus when it held and distance from today's price. It is clear what it does, but never names the nearest siblings (historico_de_preco, avaliar_preco, quedas_de_preco), which overlap with the 'has it been cheaper?' / 'is this a good price?' phrasing used here.

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?

Provides concrete trigger phrasings ('lowest price in the last 30 days', 'has it been cheaper?', 'is this the lowest price ever?') that give an agent a clear selection context. It stops short of exclusions or explicit routing to alternatives, so the agent must infer when historico_de_preco or avaliar_preco is the better call.

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