Skip to main content
Glama

Tollkit

by io.github.UltraStarz
OverviewDiscussionsAdmin

Weigh Station: check an x402 service before paying

check_service
Read-only

Free. Probes any x402 endpoint WITHOUT paying and reports what it actually charges, to which wallet, on which network, and how that compares with its public Coinbase Bazaar listing (price, recipient, distinct payers in the last 30 days). Returns facts and named signals such as pay_to_differs_from_listing; it does not score or recommend. Works for services that have nothing to do with Tollkit. Read-only: it sends one unpaid request, the way any buyer asks for a price, and never pays or changes anything.

When to use: Before paying any x402 endpoint, to see what it really charges and who gets paid. Free. Parameters: url: the endpoint. One unpaid request is sent; nothing is paid. Returns: price, network, pay-to wallet, how they compare with its Bazaar listing, and named signals such as pay_to_differs_from_listing.

Input Schema

NameRequiredDescriptionDefault
urlYesThe x402 endpoint, e.g. https://api.example.com/v1/thing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / method
      Removed value: -{
-  "description": "Force a method. By default the listed method is tried first.",
-  "enum": [
-    "GET",
-    "POST"
-  ],
-  "type": "string"
-}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint; the description adds real value on top by specifying that exactly one unpaid request is sent, that nothing is paid or changed, and that the tool returns facts and named signals without scoring or recommending. It omits rate-limit or failure behavior, keeping it out of the top band.

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 content is front-loaded and organized under When to use/Parameters/Returns, but 'Free' and 'nothing is paid' are restated three times and the Returns section largely duplicates the opening paragraph. It is readable but carries visible redundancy.

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?

With no output schema, the description compensates by enumerating the return contents (price, network, pay-to wallet, listing comparison, named signals). Only minor gaps remain, such as response format or failure handling for unreachable or non-x402 endpoints.

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% for the single url parameter, so the schema already carries the semantics and baseline is 3. The description repeats that url is the endpoint and adds that one unpaid request is sent, but no format or syntax detail beyond the schema's example.

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?

Names a specific verb (probes) and resource (any x402 endpoint) and states the exact scope: what it charges, to which wallet, on which network, versus the Bazaar listing. This is clearly distinguishable from siblings such as x402_seller_lookup or find_service.

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?

An explicit 'When to use: Before paying any x402 endpoint' plus a note that it works for services unrelated to Tollkit gives an agent a clear trigger condition. It does not name alternative tools or state when-not to use it, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tollkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources