ScorpTech x402 Tools

Poly Eval

poly_eval

Read-onlyIdempotent

Evaluate an integer polynomial at an integer point, by Horner. The zero polynomial evaluates to 0. An optional modulus reduces the result; zero is rejected. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/poly-eval

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": {
      "a": "<a>",
      "x": "<x>"
    },
    "name": "poly_eval"
  }
}

Input Schema

Name	Required	Description	Default
`a`	Yes
`x`	Yes
`mod`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the hints, the description provides crucial behavioral details, such as the specific evaluation method (Horner), the guaranteed behavior of the zero polynomial, and the operational cost and API endpoint details.

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 tool uses two concise sentences. It front-loads the core functional definition and relegates the operational/metadata (cost, URL) to the end, ensuring the agent sees the function first.

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?

Given the mathematical complexity and the lack of output schema or detailed annotations, the description provides comprehensive behavioral, functional, and operational context, making it complete for an agent to act upon.

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?

With schema description coverage at 0%, the description is vital. It clarifies that 'a' represents the coefficients of an integer polynomial and explains the functional role of the optional modulus 'mod'.

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 specifies the exact mathematical task ('Evaluate an integer polynomial') and the algorithm used ('by Horner'), making it highly precise and easily distinguishable from related mathematical tools like those dealing with sequences or factorials.

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

Usage Guidelines4/5

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

It clarifies the role of the optional 'mod' parameter by stating it 'reduces the result; zero is rejected.' This is clear guidance on usage conditions, although it does not explicitly name alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ScorpTech x402 Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?