ScorpTech x402 Tools

Parking Spots

parking_spots

Read-onlyIdempotent

Where each car parks, comma-separated. (1,1) parks at 1,2. (2,1) parks at 2,1. (1,2,1) parks at 1,2,3. A list that is not a parking function is rejected. The list has 1 to 8 entries, each from 1 to 8. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/parking-spots

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": {
      "prefs": "<prefs>"
    },
    "name": "parking_spots"
  }
}

Input Schema

Name	Required	Description	Default
`prefs`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive). The description adds important context: invalid lists are rejected, and each successful call costs $0.001 USDC via x402 on Solana, plus an HTTPS endpoint. It does not specify the response format on rejection or pagination, but the payment and validation behavior are well disclosed.

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 reasonably concise and front-loads the output description and examples. The payment details and URL are placed at the end, which is appropriate, though the examples could be slightly more compact.

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 read-only computation with one parameter and no output schema, the description adequately covers input constraints, output format hint ('comma-separated'), validation behavior, and payment. It could be clearer on the exact return type (string vs array) and on what happens when a list is rejected, but it is largely complete.

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 0%, so the description must compensate. It provides examples like (1,1) parks at 1,2 and notes the list has 1-8 entries each 1-8, which clarifies the prefs parameter's expected input and mapping. However, it never explicitly states that each entry is a car's preferred spot, leaving some ambiguity.

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 gives examples mapping an input list to parking spots, making the function's purpose understandable. However, it lacks an explicit verb like 'compute' or 'validate', and it does not differentiate from sibling tools such as parking or parking_moved, so an agent might confuse it with related parking functions.

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?

No guidance is provided on when to choose this tool versus the parking, parking_moved, parking_shift, or parking_witness siblings. The description only states input constraints and rejection behavior, leaving usage context implied.

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?