Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_ecom_price_drop_comparator

Compare price histories or old and new prices to flag drops, lows, and target-price hits for informed buy decisions.

Instructions

[E-Commerce Intelligence] Compare a price series (or old/new price) and flag drops, lows and target hits Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://ecom.caelaralabs.com.

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": "caelara_ecom_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 observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral load. It does disclose latency (p50 11 ms, p95 15 ms) and the backing endpoint, which helps the agent judge cost and reliability. It does not say whether the call is read-only, what happens on malformed or empty series, or how a 'target hit' is reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in a single tight clause, which is good. The trailing benchmark and endpoint sentence, especially the full URL, is boilerplate that consumes space without helping the agent decide or invoke. The whole thing is short, but not every sentence earns its place.

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?

There is no output schema, so the description should sketch the return shape. "Flag drops, lows and target hits" only gestures at it. Combined with silent ambiguity about which inputs are required, the definition is adequate but leaves real gaps for a five-parameter comparison 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 100%, so the schema already documents all five parameters, which sets a baseline of 3. The description adds only marginal value by flagging that a series or an old/new pair are alternative inputs. With zero required parameters, the agent gets no cue about which combination is valid or what the defaults produce.

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 names a specific verb and resource: "Compare a price series (or old/new price) and flag drops, lows and target hits." That is clear enough to distinguish it from the crypto aggregator and the margin calculator siblings. It stops short of 5 only because it does not explicitly contrast itself with any named alternative.

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 two supported input modes and therefore when each parameter family applies, which is useful implied guidance. However, the description never states when to prefer this tool over siblings, and gives no prerequisites or exclusions. Usage guidance is inferred rather than stated.

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

Deploy Server

Other Tools