Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

ping

[x402 paid: $0.001 USDC on Base] Liveness ping: pong + server unix time. Health-check helper for agent pipelines. tools/call returns the live payment challenge.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses the x402 payment cost ($0.001 USDC on Base) and explains that tools/call returns a live payment challenge, which is critical non-obvious behavior for an agent. It omits details such as whether retries are charged again or how the challenge is satisfied, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short, front-loaded sentences: payment tag, what it returns, then usage role. Every clause carries information an agent needs, and the cost disclosure sits first where it will not be missed.

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, no-output-schema tool, the description covers return values, intended use, and the payment flow. Remaining gaps (timestamp format, challenge mechanics) are minor and largely self-evident for a liveness endpoint.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It appropriately spends no words on parameter semantics.

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?

States a concrete verb and resource — a liveness ping returning 'pong + server unix time' — plus its role as a health-check helper. It distinguishes itself from the sibling 'time' tool by pairing the timestamp with a liveness round-trip, though it doesn't say so explicitly.

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?

'Health-check helper for agent pipelines' implies the use case, which is enough to know it is for liveness probing rather than data retrieval. No explicit exclusions or comparison to alternatives like the 'time' or 'tick' siblings, so guidance remains implied 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.

Resources