Skip to main content
Glama

dipscout

by com.dipscout
OverviewDiscussionsAdmin

Detected price drops

quedas_de_preco

Products whose price dropped at least 15% and $3 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), or that hit their lowest recorded price. Requires 3 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.

Input Schema

NameRequiredDescriptionDefault
idiomaNoOptional 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.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. 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"
+}
  2. 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"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Since no annotations are present, the description must carry the full behavioral burden. It does this by explicitly detailing the 'verified' vs 'none' certainty status and warning the agent against misinforming the user. This disclosure of data integrity rules is highly valuable.

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 dense but not wasteful; every sentence contributes critical, non-redundant information (e.g., flash sale caveat, definition of certainty). While verbose, the structure logically builds the definition from calculation criteria to presentation guidelines.

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?

Given the complexity of the underlying metrics (time-weighted median, multi-criteria thresholds), the description is remarkably complete. It explains the methodology, the constraints, and the reliability of the results.

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?

The description does not add unique semantic value to the input parameters (idioma, limite, mercado), which are sufficiently covered by the schema descriptions. It does, however, provide crucial context regarding the tool's outputs which indirectly relates to parameters.

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?

The description is extremely precise, defining exactly what constitutes a 'price drop' (15% and $3 below typical price, or lowest recorded price). This high level of mathematical specificity clearly distinguishes the tool's function from general promotion searching.

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

Usage Guidelines5/5

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

It sets strict conditions for use, such as requiring 3 days of tracking and defining the scope of the data based on time-weighted medians. It manages user expectations about the data quality (e.g., explaining that the seller's listed price is not considered in the calculation).

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