ScorpTech x402 Tools

Text Fit

text_fit

Read-onlyIdempotent

Largest Helvetica size, on a fixed step, at which one line still fits a width. Sizes run from minSize to maxSize in steps (defaults 6, 72 and 0.5 points). Empty text fits at maxSize. If the line does not fit at minSize, the call is rejected. Width uses the same AFM rounding as text-width, so the size is not a float division of the two widths. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/text-fit

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_fit"
  }
}

Input Schema

Name	Required	Default
`font`	No	helvetica
`step`	No	0.5
`text`	Yes
`width`	Yes
`maxSize`	No	72
`minSize`	No	6

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly, idempotent, non-destructive) by disclosing the paid x402/Solana pricing, the failure/rejection mode, empty-input behavior, the AFM rounding caveat that makes results non-obvious, and an equivalent HTTPS endpoint. This is rich behavioral context an agent cannot get from structured fields.

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?

Front-loads the core computation in the first sentence, then adds only high-value clauses: defaults, edge cases, rounding caveat, pricing and alternate endpoint. Dense with no filler.

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 6-param tool with no output schema, it covers defaults, failure modes and pricing thoroughly. The return value is only implied (the resulting size) rather than stated, and the font enum is unaddressed, leaving minor gaps.

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 load and does well: it explains minSize, maxSize and step defaults (6, 72, 0.5 points) and the role of text and width. It omits the font enum (helvetica vs helvetica-bold), so one of six parameters remains unexplained anywhere.

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?

States a precise verb+resource: computes the largest Helvetica size at which one line fits a given width, on a step grid. It is clearly distinguishable from siblings like text_width (measurement) and text_wrap (layout) because it explicitly targets a size search and even references the text-width rounding model.

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?

Explains key edge conditions: empty text yields maxSize, and if the line does not fit at minSize the call is rejected. It does not explicitly route to alternatives (e.g. use text_width if you only need a measurement), so the when-not guidance is implicit rather than spelled out.

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?