ScorpTech x402 API

Mode Diff

mode_diff

Read-onlyIdempotent

Bits that differ between two POSIX modes. added and removed run from the special bits down through owner, group and other. same is true when nothing differs. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/mode-diff

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "mode_diff"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes
`from`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds useful context: output fields, ordering of added/removed bits, the meaning of 'same', payment cost, and an alternate HTTPS endpoint. This adds real behavioral value beyond the annotations, though it does not describe auth requirements in more detail or input representation.

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 purpose before output details and pricing. The payment and alternate-endpoint information is relevant for this paid tool, though it adds some operational overhead.

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 simple two-parameter diff tool with no output schema, the description does a fair job explaining the return fields. However, it leaves the input mode format ambiguous and does not fully specify how added/removed bit sequences should be interpreted. It is adequate but has clear gaps.

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 carry parameter semantics. It indicates that the inputs are POSIX modes, but it does not state the expected format for 'from' and 'to' (for example octal like 755 versus symbolic like rwxr-xr-x), which is important for correct invocation.

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 a specific operation and resource: computing differing bits between two POSIX modes. It also names the output partitions (added, removed, same). It does not distinguish this tool from related siblings such as chmod_apply, file_mode, umask_mode, or permission_check.

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 related mode/permission tools. The output behavior is described, but no usage context, prerequisites, or alternatives are named. An agent must infer that this is for comparing two mode values.

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?