ScorpTech x402 API

Text Block

text_block

Read-onlyIdempotent

Wrap a Helvetica block and give its height. Line breaking is the same as text-wrap. Leading defaults to 1.2 times the font size, rounded half away from zero to 0.001 pt. Block height is the line count times the leading, and a blank line from a hard break counts. An empty string has height zero. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/text-block

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": {
      "text": "<text>",
      "width": "<width>"
    },
    "name": "text_block"
  }
}

Input Schema

Name	Required	Description	Default
`font`	No		helvetica
`size`	No		12
`text`	Yes
`width`	Yes
`leading`	No	Line height in points. Default is 1.2 × size

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: x402 payment terms ($0.001 USDC per successful call on Solana), an HTTPS fallback endpoint, rounding rules, and the empty-string edge case. It does not describe the actual response payload shape.

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?

Front-loaded with the core action, then tight rules, then pricing/auth. Nearly every sentence earns its place, though the pricing/endpoint sentence is dense and could be split for scannability.

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?

With no output schema, the description carries the return-value burden and does so by giving the exact height formula and edge case. Combined with annotations covering safety and the description covering cost/auth, an agent has what it needs to invoke correctly.

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

Parameters3/5

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

Schema description coverage is only 20%, so the description must compensate. It clarifies leading (default 1.2× size, rounded half away from zero to 0.001 pt) and implies size is in points, but leaves the units and semantics of width and size, plus the text length limit, undocumented. Partial compensation only.

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?

States a specific verb and resource: wrap a Helvetica text block and return its height. Referencing 'text-wrap' for line-breaking ties it to the sibling family, and the height formula makes the output concrete. It stops short of explicitly distinguishing itself from text_width or text_fit.

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 text-wrap line-breaking reference and by the height-computation focus, but there is no explicit statement of when to choose this over text_width, text_fit, or text_wrap. An agent must infer the routing.

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?