Skip to main content
Glama

Kingdom of Kantrom

pedir_sello

How to buy a Kantrom timestamp seal (0.10 USDC via x402) for a SHA-256 digest: returns the paid endpoint and the exact payment requirements.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sha256": "<sha256>"
    },
    "name": "pedir_sello"
  }
}

Input Schema

NameRequiredDescriptionDefault
sha256YesSHA-256 hex digest (64 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the cost (0.10 USDC), the payment protocol (x402), and crucially that the tool returns the paid endpoint plus payment requirements rather than performing the purchase itself. It stops short of explaining who executes the x402 payment flow or what happens on an unpaid/invalid digest.

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?

One tight sentence, front-loaded with the action and cost, followed by the return behavior. Nothing is redundant or padding.

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 one-parameter tool with no output schema, the description covers cost, protocol, input, and return value, which is close to what an agent needs. The remaining gap is the mechanics of the x402 payment (whether the agent must settle payment separately) and behavior on an invalid digest.

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?

There is a single parameter at 100% schema description coverage ('SHA-256 hex digest (64 chars)'), so the schema already fully documents it. The description only restates that a digest is the input, adding no format or validation detail beyond the schema.

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 gives a specific verb and resource ('buy a Kantrom timestamp seal') scoped to a SHA-256 digest, and states what the call actually produces ('returns the paid endpoint and the exact payment requirements'). It implicitly separates itself from verificar_sello (verification) by framing this as the purchase path, though it never names a sibling 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?

Usage is implied ('How to buy...') but there is no explicit when-to-use/when-not or named alternative such as verificar_sello for checking an existing seal. An agent can infer the context, but the routing decision is left to inference.

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