Skip to main content
Glama

Storefront Agent Readiness Payment Quote

storefront_readiness_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/storefront/agent-readiness (base $0.02; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?url=https://shop.example.com/product (one public product page). Storefront agent readiness: score one product page 0-100 for HTTP status, bot walls, robots.txt AI rules, JS-only rendering, structured price and product schema, with fix notes. GET ?url= or POST {url}. Refused calls are not charged: a bad or private URL, a timeout, an unreachable site, a cross-origin redirect, a URL our crawler may not fetch under robots.txt, or our own rate limits. A report on a page that answers with a bot wall, an HTTP error or a redirect loop is charged. USDC on Base only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description's extra value is in the payment and billing model: $0.02 in USDC on Base only, x402 v2, and a detailed charged-vs-not-charged policy covering bad/private URLs, timeouts, cross-origin redirects, robots.txt blocks and rate limits. One caveat: much of that billing detail describes the downstream paid call rather than this quote tool itself, so the reader must disentangle which rules apply to which step.

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 most decision-relevant facts (price, network, 'never runs the check or pays') are front-loaded, which is correct. But the prose is dense with semicolons and stacked parentheticals, and the refusal/charge list is a long run-on that could be a bulleted set, costing readability.

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?

For a zero-parameter quote tool with no output schema and full annotation coverage, the description supplies price, network, protocol, invocation shape and charging policy — enough for an agent to act. It does not describe the quote response itself (what the 402 body/terms look like beyond 'x402 v2'), which is the main remaining gap.

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?

The input schema is empty, so the baseline is 4; the description still adds call-shape meaning by specifying GET ?url= or POST {url} and that the URL must be one public product page. That said, those invocation details belong to the paid endpoint, not this zero-parameter tool, so the added meaning is contextual rather than strictly about this tool's inputs.

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 opening sentence names a specific resource (payment terms for the storefront agent-readiness endpoint) and immediately disclaims behavior: 'this tool never runs the check or pays.' It also scopes the underlying service to 'score one product page 0-100,' which separates it from generic readiness tools. It stops short of naming which sibling to use for non-storefront pages.

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 the flow (get a quote, then pay the 402 over HTTP with x402 v2) but never states explicitly when to choose this tool over siblings such as agent_readiness_quote or fetch, nor any precondition like 'call this first if you do not already have a quote.' Usage is inferable rather than stated.

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.