Skip to main content
Glama

Champernowne Digit

champernowne_digit
Read-onlyIdempotent

The digit in place pos of 123456789101112..., counting from 1. Place 9 is 9, place 10 is 1, place 11 is 0, and place 190 is 1. pos runs from 1 to 999999999999. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/champernowne-digit

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": {
      "pos": "<pos>"
    },
    "name": "champernowne_digit"
  }
}

Input Schema

NameRequiredDescriptionDefault
posYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it read-only, idempotent, non-destructive and open-world. The description adds genuinely new context: the per-call price ($0.001 USDC via x402/Solana) and an alternate HTTPS endpoint, which an agent needs to call it correctly.

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?

Front-loaded with what it computes before examples, range, and pricing/transport. Each piece earns its place, though the inline examples add some length that a tighter spec could compress.

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 simple one-parameter read tool with no output schema, this covers the computation, valid range, examples, cost, and endpoint. The return value (a single digit 0-9) is implied rather than stated explicitly, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full load. It explains the parameter means a 1-based positional index into the concatenated string and provides concrete examples (place 9=9, 10=1, 11=0, 190=1), far beyond the schema's bare min/max integers.

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 specific resource and scope ('The digit in place pos of 123456789101112...') with worked examples that make the operation concrete. It does not differentiate from close siblings like champernowne_place or champernowne_owner, which an agent would need to distinguish it from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The examples clarify what the tool computes but there is no explicit when-to-use, when-not-to-use, or comparison to the nearby champernowne_* siblings. An agent must infer usage entirely.

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