Skip to main content
Glama

URL Unwrap Payment Quote

url_unwrap_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/url/unwrap (base $0.003; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?url=https://bit.ly/example (one http(s) URL, ports 80/443; optional headOnly=true; follows up to 8 redirects, lower hop limits are not supported). URL unwrap: follows a short or wrapped link's redirects with HEAD requests (8 s) and returns each hop's URL and status, the final URL and whether it crossed domains. Follows up to 8 redirects; lower hop limits are not supported. Charged only when the chain resolves. A loop, more than 8 redirects or a non-web Location is not charged; nor are blocked targets, unreachable hops or bad input. It is a visit: do not submit one-time or sign-in links. Not a safety verdict. 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": "url_unwrap_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?

The description goes well past the annotations by disclosing the price ($0.003), the settlement asset and chain (USDC on Base only), the 8-second HEAD timeout, the 8-redirect ceiling, and precisely which outcomes are not billed (loops, over-limit redirects, non-web Location, blocked targets, unreachable hops, bad input). That billing detail is exactly the kind of behavior an agent cannot infer from readOnlyHint/idempotentHint. Minor deduction for mild tension with openWorldHint=false, since the described behavior follows external links across domains.

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 pricing and prohibitions are front-loaded well, but the text is cluttered by repetition: 'Follows up to 8 redirects; lower hop limits are not supported' appears twice in near-identical wording, and 'USDC on Base only' is stated at both the top and the bottom. The dense parentheticals in sentence one make the core offer harder to parse than it needs to be.

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, it covers pricing, protocol, redirect limits, and non-charged failure modes, which is close to what an agent needs to decide and act. The remaining gap is the shape of the returned terms and how the url parameter is actually transmitted.

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 schema is empty, so the description carries the entire burden and does supply the operative inputs: a single http(s) URL restricted to ports 80/443, and an optional headOnly=true flag. It does not clarify how those are surfaced given a zero-property input schema, leaving an agent to infer they belong on the paid HTTP request rather than in the tool call.

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 first clause states a specific verb and resource: it returns payment terms for the URL-unwrap endpoint at horizonpulse.dev. It also disambiguates the quote from the work itself ('this tool never runs the check or pays'). It loses a point because the remainder of the text describes the underlying unwrap operation in detail, blurring whether the reader is buying a quote or a redirect trace.

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?

There is real conditional guidance: pay the 402 over HTTP with x402 v2, one http(s) URL only, optional headOnly=true, ports 80/443, and an explicit exclusion ('It is a visit: do not submit one-time or sign-in links'). What is absent is routing against alternatives, such as when to use this quote versus the sibling 'http' tool, or what to do when the input is not a shortener link.

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.