Skip to main content
Glama

x402-is-disarium-number

Is Disarium Number: Validates a disarium number where value equals its positional digit powers sum 🆓 5 free trial calls per signed wallet

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": "x402-is-disarium-number"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / value / description
      Removed value: -"Value to process"
  2. Changed1 schema field changed
    • addedInput schema / properties / value
      Added value: +{
      +  "description": "Value to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add one genuine behavioral trait beyond the schema by disclosing the payment model ('5 free trial calls per signed wallet'), implying a x402 metered endpoint with wallet auth. However it says nothing about the return shape (presumably a boolean/valid flag), error behavior for non-numeric input, or what happens after the trial quota.

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?

The core definition is front-loaded in a single clear clause. The trailing free-trial/emoji line is boilerplate but brief and does convey cost information, so it is not pure waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a trivial single-argument predicate with no output schema, the description gives enough to run the tool and defines the mathematical term. It is incomplete on the input format and the response value, which for a validation tool is the main thing an agent needs to interpret the result.

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?

One parameter ('value') with 0% schema description coverage, so the description must compensate. It implies the input is the number being tested via 'value equals its positional digit powers sum', which is mild added meaning, but it never states format constraints such as whether it must be a positive integer string or how leading zeros affect positional indexing.

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 verb (validates) and resource (disarium number), and even defines the property: 'value equals its positional digit powers sum'. That makes the predicate unambiguous without opening the schema. It does not distinguish itself from the near-identical sibling x402-is-disarium, which is the only gap.

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?

There is no when-to-use context, no prerequisites for the input, and no reference to alternatives such as x402-is-disarium or x402-is-narcissistic-number. The agent is left to infer the use case from the name alone.

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