ScorpTech x402 API

Bezier Split

bezier_split

Read-onlyIdempotent

Split a quadratic or cubic Bezier at t by de Casteljau. Left and right are the two new control polygons, and they meet at the point on the curve. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/bezier-split

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": {
      "points": "<points>",
      "t": "<t>"
    },
    "name": "bezier_split"
  }
}

Input Schema

Name	Required	Description	Default
`t`	Yes
`points`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable non-annotation context: the call costs $0.001 USDC via x402 on Solana and is also available over HTTPS at a specific endpoint.

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 purpose is front-loaded in the first sentence, followed by useful output semantics and payment/endpoint details. There is no filler; each sentence contributes either to understanding the operation or to invoking the paid endpoint correctly.

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?

The description explains the conceptual return value even though no output schema exists, and annotations cover the safety profile. However, with no schema descriptions and no parameter-format details, it is only partially complete for correct invocation, especially for the points array and t format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the two undocumented parameters. It mentions t as the split parameter and implies the input is control points for a quadratic or cubic Bezier, but it does not explain the coordinate format, expected point count, or t constraints.

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 gives a specific verb and resource: split a quadratic or cubic Bezier at parameter t using de Casteljau. It also explains the output as two new control polygons meeting at the curve point, making the operation clearly distinct from sibling curve-evaluation tools like bezier_cubic and bezier_quadratic.

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?

The description does not state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites beyond the payment note. An agent can infer that it is for Bezier subdivision, but there is no explicit usage guidance.

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

All ScorpTech x402 API 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?