Skip to main content
Glama

ScorpTech x402 Tools

Rising

rising
Read-onlyIdempotent

The rising factorial n^(k) = n*(n+1)...(n+k-1). 5^(3) is 210, and 5^(0) is 1. n runs from 0 to 100000 and k runs from 0 to 512. Past 15 digits the value is a decimal string. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/rising

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": {
      "n": "<n>",
      "k": "<k>"
    },
    "name": "rising"
  }
}

Input Schema

NameRequiredDescriptionDefault
kYes
nYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety traits (readOnly, idempotent, openWorld, non-destructive), and the description adds important behavior: pricing at $0.001 USDC per successful call, x402/Solana payment context, an HTTPS endpoint, and decimal-string output past 15 digits.

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?

The description is front-loaded with the definition and examples, then covers bounds, output format, and payment details in compact sentences. Every sentence provides useful information.

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 two-parameter math tool with no output schema, the description supplies the formula, examples, bounds, output representation for large values, and pricing context. The exact response envelope is not specified, but the core computation and return format are sufficiently clear.

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?

With 0% schema description coverage, the description carries the burden well: it defines n and k through the rising-factorial formula, gives an example, and states valid ranges. It does not add much beyond the schema's own numeric bounds, but the mathematical meaning is clear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific mathematical operation, gives its exact formula, and provides concrete examples (5^(3)=210, 5^(0)=1). This clearly distinguishes rising factorial from siblings such as falling factorial.

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?

The operation definition implies when the tool is appropriate, but there is no explicit guidance about when to use it versus alternatives such as falling factorial or other factorial-related tools. The domain bounds and output note help invocation but are not usage guidance.

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