Skip to main content
Glama

DealMonitor

check_price

Read the current price of a product from its shop URL. Works on shops that block simple HTTP requests, because the page is fetched server-side with a real browser when needed. No account required. Can take up to two minutes on a slow shop.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "check_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the page is fetched server-side with a real browser when simple HTTP is blocked, that no authentication is needed, and that a call can take up to two minutes. Missing are failure behavior (e.g. non-product or unreachable URLs) and any rate-limit or reliability note.

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?

Four short sentences, each adding a distinct fact: purpose, fallback mechanism, auth requirement, and latency. Purpose is front-loaded and there is no filler or repetition.

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?

An output schema exists, so return values need no explanation, and the definition covers the operationally important surprises (slow execution, browser fallback, no account). Only error/edge-case behavior on invalid or non-product URLs is left unaddressed.

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 coverage is 0% for the single parameter, so the description must compensate. It clarifies that the url is a product page on a shop rather than a generic endpoint, which is meaningful, but it gives no format example or hint about what a valid product URL looks like.

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?

States a specific verb and resource ("Read the current price of a product") scoped to a shop URL. The word "current" implicitly separates it from the historical sibling price_history, and the other siblings (set_target_price, watch_price, stop_watching) are clearly different operations, so an agent can choose without opening the schema.

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?

Usage context is implied rather than stated: it is the tool for getting a price right now, and "no account required" plus the blocking-shop note tell the agent it is safe to use broadly. There is no explicit statement of when to prefer price_history or watch_price instead, nor any prerequisite or exclusion.

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