Skip to main content
Glama

ScorpTech x402 Tools

Bezier Derivative

bezier_derivative
Read-onlyIdempotent

Control points of the derivative of a quadratic or cubic Bezier. A cubic derivative is a quadratic, and each control is the degree times the step to the next point. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/bezier-derivative

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>"
    },
    "name": "bezier_derivative"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior. The description adds meaningful behavioral context beyond annotations: the cost per successful call, x402/Solana payment rail, and an equivalent HTTPS endpoint.

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?

The description is compact and front-loads the core operation. The extra sentence about cubic derivatives is educational and the pricing/endpoint details are useful, though not strictly part of the mathematical definition.

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 single-parameter math tool with no output schema, the description covers purpose, pricing, and an alternate endpoint. However, it leaves the input format and return structure underspecified, which matters given the lack of schema descriptions.

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% and the only parameter, points, is not explained in terms of format or item shape. The description mentions control points for quadratic or cubic curves, but it does not clarify whether input points are coordinate pairs or how the array should be structured.

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?

The description clearly states that the tool returns control points of the derivative of a quadratic or cubic Bezier curve. The resource and operation are specific, but it does not explicitly distinguish itself from nearby siblings such as bezier_tangent or bezier_split.

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 explicit guidance on when to use this tool versus alternatives. The mathematical context implies a use case, but no conditions, exclusions, or sibling comparisons are provided.

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