Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-is-woodall

Is Woodall: Checks whether value equals k*2^k-1 for some integer k, returning a boolean 🆓 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-woodall"
  }
}

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. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the return type ('returning a boolean') and payment/access context ('5 free trial calls per signed wallet'), but says nothing about how the string input is parsed, behavior on non-numeric or negative input, or handling of very large values.

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?

One compact sentence that front-loads the definition, followed by a short access/pricing note. No filler, though the emoji trial line is decorative rather than definitional.

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 simple boolean predicate with no output schema, the essential return behavior is stated, but the description leaves the input contract (string format, edge cases) unspecified and offers no routing information among the dozens of similar is-* predicates.

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?

The single parameter has 0% schema description coverage, so the description must compensate. It implies 'value' is the integer being tested via the formula, but never specifies the accepted format (plain decimal string, hex, size limits) — leaving the string-typed parameter under-explained.

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 predicate and gives the exact formula (value equals k*2^k-1 for some integer k), so an agent knows precisely what is being tested. It does not distinguish itself from near-twin siblings like x402-is-cullen (k*2^k+1) or x402-is-carmichael, which the agent must infer from the name alone.

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 or when-not-to-use guidance and no named alternative among the many sibling number-property predicates. Usage is only implied by the formula itself.

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.