Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-golden-ratio

Golden Ratio: The golden ratio constant. Takes no parameters. Returns (1+sqrt 5)/2 as result. 🆓 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-golden-ratio"
  }
}

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 full burden and does reasonably well: it discloses that the tool takes no parameters, is a pure computation, and reveals the exact return formula. It also adds billing context (5 free trial calls per signed wallet), which is genuine operational information an agent would not otherwise know. It stops short of stating precision or output type.

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?

Three short sentences, front-loaded with the identity, then inputs, then output. The emoji trial-call line is marketing-flavored but conveys real quota information, so it earns its place.

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

Completeness5/5

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

For a trivial constant-returning tool with no output schema, the description covers identity, input arity, the exact returned value, and a usage quota. Nothing an agent needs in order to call it correctly is missing.

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?

Zero-parameter tool, so the baseline is 4; the description confirms "Takes no parameters," which matches the empty schema. Nothing further is needed.

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?

"Golden Ratio: The golden ratio constant" names the resource, and the description states exactly what is produced: (1+sqrt 5)/2. It is clear enough to distinguish from arithmetic siblings like x402-ratio-of or x402-ratio-simplify, though it never explicitly contrasts itself with them.

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 by the fact that this is a constant lookup with no inputs; there is no stated when/when-not or pointer to an alternative. For a zero-argument tool the risk of misselection is low, so implied guidance is adequate but not strong.

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.