Skip to main content
Glama

Check one product page now (paid, no quota)

live_check
Read-onlyIdempotent

Paid: US$0.005 per call in USDC over x402 (or 5 prepaid credits), with no monthly quota. Fetch one retailer product page now and return whether it still exists, its current price and stock. Not charged if the page could not be read. Without payment the result is an x402 payment request; attach the signed payment at _meta["x402/payment"] and call again. check_product_link does the same within the free monthly allowance.

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

Input Schema

NameRequiredDescriptionDefault
urlYesProduct page url on a retailer exNiche covers, e.g. the url of a search result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and idempotent, so the safety profile is covered; the description adds genuinely new behavior: per-call pricing, no charge on unreadable pages, and the x402 payment-request handshake via _meta["x402/payment"]. It does not describe latency or rate limits, but the payment and failure semantics are the important disclosures here.

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

Conciseness4/5

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

Front-loads the pricing model, then the action, then the payment mechanics and the alternative. Dense but every sentence carries information; the payment-retry sentence is slightly compressed but not wasteful.

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?

With no output schema, the description still names the return values (existence, price, stock) and explains the non-success path (payment request, no charge). Nothing an agent needs to invoke and interpret the call is missing.

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 100% and the single url parameter is already documented with its maxLength and example. The description adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 ('Fetch one retailer product page now') plus the exact return payload (existence, current price, stock), and distinguishes itself from check_product_link by the paid/no-quota model. An agent can tell it apart from the free sibling without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use this for paid, no-quota single-page checks, and 'check_product_link does the same within the free monthly allowance' names the alternative and the condition that selects it. The payment retry path is also spelled out.

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