Skip to main content
Glama

pricewatcha

by io.github.pricewatcha

Get price history

get_price_history
Read-onlyIdempotent

Get historical prices, aggregates (low/high/average), trend, and data points for a product. On failure, returns a structured error object with fields error.code, error.message, error.http_status, error.retry_recommended, and error.retry_after_seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idYesPublic product ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
trendNo
previewNo
currencyYes
product_idYes
data_pointsYes
average_priceNo
current_priceNo
historical_lowNo
historical_highNo

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds valuable context about structured error objects on failure and mentions return components (aggregates, trend), going beyond annotations without contradiction.

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?

Two sentences with no wasted words. First sentence covers purpose and return, second covers error handling. Very efficient.

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?

Given low complexity, annotations, and output schema, the description adequately covers purpose and key behaviors. However, it omits potential constraints like date range limits or pagination, which could be relevant.

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% with 'Public product ID' for product_id. The description does not add any additional meaning to the parameter beyond the schema, so baseline 3 is appropriate.

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 clearly states the verb 'Get' and the resource 'historical prices' for a product, specifying return types (aggregates, trend, data points). It naturally distinguishes from siblings like get_product or search_products.

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 description implies usage for retrieving price history but lacks explicit guidance on when to use this tool versus alternatives (e.g., get_product) or any exclusion criteria.

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

All pricewatcha toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool clearly maps to a distinct resource and action: price alert CRUD verbs (create/get/list/update/delete) are unambiguous, and get_api_status vs get_job_status are separated by scope (service health vs async job polling). track_product, search_products, get_product, and get_price_history each address a different part of the product workflow with no meaningful overlap.

Naming Consistency5/5

All 11 tools follow a consistent verb_noun snake_case pattern: create_price_alert, get_price_history, track_product, list_price_alerts, and so on. Verbs are precise and nouns are stable across the set, making the API surface predictable.

Tool Count5/5

At 11 tools, the server is well-scoped for its purpose: alert management, product search, price history, tracking, and status checks each earn their place. No tool feels redundant or excessive for a price-intelligence domain.

Completeness4/5

The price alert lifecycle is fully covered with create/get/list/update/delete, and product search/tracking/history are solid. A minor gap is the lack of a way to list or stop all tracked products/jobs besides polling a known job_id, but this can be worked around and core workflows are complete.

Resources