Skip to main content
Glama

pricewatcha

by io.github.pricewatcha

Get job status

get_job_status
Read-onlyIdempotent

Poll an async tracking job by job_id. Returns status (queued, running, completed, or failed). On completion, product is populated; on scrape failure, error is populated (HTTP 200 job lookup — not a transport error). 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
job_idYesJob ID from track_product

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
errorNo
job_idYes
statusYes
productNo

TDQS

A4.5/5.0
Behavior4/5

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

Beyond annotations (readOnly, idempotent), it clarifies that HTTP 200 indicates job lookup success, not a transport error, and details the error object structure on failure. No contradiction with annotations.

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?

Three concise sentences with no filler. Front-loaded with core purpose, immediately actionable.

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 output schema exists, the description covers all necessary states (statuses, populated fields on completion/failure) and error details, making it complete for a polling tool.

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 already describes job_id with 100% coverage; description adds extra context that job_id comes from track_product, which aids understanding beyond the schema.

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 starts with a specific verb ('Poll') and resource ('async tracking job by job_id'). It lists exact statuses and outcomes, clearly distinguishing from siblings like get_product or get_api_status.

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?

It implies usage after initiating a tracking job (job_id from track_product) and explains behavior for completion and failure, but does not explicitly exclude use cases or mention when not to use.

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