Skip to main content
Glama

Inspect SML Gateway Status

sml_status
Read-onlyIdempotent

Inspect live x402 Gateway status (FREE, read-only). Returns readiness, the active tool profile, the registered gateway tool names, a check timestamp, and the same canonical contract as sml_discover: x402 v2 exact scheme, USDC on Base mainnet (eip155:8453), the canonical payTo, and the payment headers. Use it to confirm the gateway is up and which rail is authoritative before probing paid routes.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds real context beyond them: that the call is FREE, and the concrete contents of the response (readiness, profile, tool names, timestamp, contract constants). It stops short of describing failure/error behavior when the gateway is down, which matters for a status probe.

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?

Two sentences, front-loaded with the verb and the FREE/read-only qualifier, then a structured enumeration of return contents and a usage sentence. The enumeration is long but each item is distinct information; only the repeated canonical-contract detail (x402 v2, eip155:8453, payTo) borders on redundant for a status check.

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 and no parameters, the description carries the return-value burden and does so by naming each field returned plus the contract constants. Minor gaps remain: "readiness" and "active tool profile" are not defined, and there is no indication of what a non-ready or failed status looks like.

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 has zero properties, so there is no parameter meaning to add; the baseline of 4 applies. The description correctly implies a no-argument call and spends its words on semantics the schema cannot carry.

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 ("Inspect live x402 Gateway status") and then enumerates exactly what it returns: readiness, active tool profile, registered gateway tool names, timestamp, and the canonical contract. It also positions itself relative to sml_discover by saying it exposes the same canonical contract, so an agent can tell the two apart 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 Guidelines4/5

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

Gives an explicit use case: "confirm the gateway is up and which rail is authoritative before probing paid routes," which also establishes ordering relative to paid-route tools. It does not state a when-not or name a competing status-check alternative, but the sequencing guidance is clear.

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