Skip to main content
Glama

Caelara Labs E-Commerce Intelligence

price_drop_comparator

Compare a price series (or old/new price) and flag drops, lows and target hits

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

Input Schema

NameRequiredDescriptionDefault
pricesNoPrice history, oldest first (numbers or {price,date})
new_priceNoCurrent price
old_priceNoPrevious price
target_priceNoTarget buy price
threshold_pctNoDrop/increase threshold percent (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the analytical outputs (drops, lows, target hits), which implies a non-mutating read/analysis tool, but it does not state the return shape, whether results are ordered, or what happens with an empty or single-element series.

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?

One short sentence with the primary purpose front-loaded and the alternate input form kept in a tight parenthetical. Nothing is wasted.

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

Completeness3/5

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

With no output schema and five all-optional parameters, an agent still cannot tell what the response looks like or how the flags are represented. The description covers the input contract adequately but leaves the output side of a purely analytical tool underspecified.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds genuine meaning by signalling that 'prices' and 'old_price'/'new_price' are alternative input modes rather than all required together - important since the schema marks zero parameters required. It does not clarify threshold behaviour beyond the schema's default note.

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 opens with a specific verb and resource ('Compare a price series') and enumerates the results it produces: drops, lows and target hits. It is more concrete than a bare name restatement, though it does not position itself against any sibling tool.

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?

The parenthetical '(or old/new price)' implies the two accepted input modes, which is the closest thing to usage guidance present. There is no statement of when to prefer this over alternatives such as currency_margin_calc, nor any preconditions or exclusions.

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