Skip to main content
Glama

Discover SML x402 Gateway

sml_discover
Read-onlyIdempotent

Discover the SCRIPTMASTERLABS x402 Gateway contract (FREE, read-only). Returns the gateway's job, transport, and canonical payment contract — x402 v2, exact scheme, USDC on Base mainnet (eip155:8453), the canonical payTo, and the PAYMENT-REQUIRED / PAYMENT-SIGNATURE / PAYMENT-RESPONSE headers — plus where to inspect fresh per-route payment requirements before calling a paid route (tools/list on this endpoint, or GET /x402/discover). The gateway never spends for the caller: read the fresh target 402 challenge for the exact price and terms; a challenge or a signature is not settlement proof.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world, so the description builds on that rather than repeating it: it adds the key semantic disclaimer that the gateway never spends for the caller and that a 402 challenge or signature is not settlement proof. That is meaningful behavior no annotation conveys.

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?

It is front-loaded with the core purpose and free/read-only tag, which is good. The middle sentence is a dense run-on that packs the protocol version, scheme, chain ID, payTo, and three header names into one long clause, making it harder to scan than necessary.

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 takes on the burden of explaining what comes back and does so with concrete specifics: x402 v2, exact scheme, USDC on Base mainnet, canonical payTo, and the three payment headers. The one gap is not naming the exact call to refresh per-route requirements beyond 'tools/list on this endpoint or GET /x402/discover', which is slightly ambiguous about which endpoint that means.

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?

Zero parameters, so the baseline is 4. The description doesn't need parameter guidance and correctly spends its words on return content and disclaimers instead.

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 description states a specific verb and resource: it discovers the SCRIPTMASTERLABS x402 Gateway contract and enumerates what it returns (job, transport, canonical payment contract, headers). It doesn't explicitly differentiate itself from sibling x402_contract, though the concrete field list helps an agent infer the split.

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?

It implies this is the free read-only entry point and points to inspecting fresh per-route payment requirements before calling a paid route, which is genuine usage context. But it never states when not to use it or names a specific alternative tool to call instead.

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