ScorpTech x402 API

Umask Mode

umask_mode

Read-onlyIdempotent

Mode of a file or directory created under a umask. A file starts from 666 and a directory from 777, then the umask bits are cleared. 022 makes a file 644 and a directory 755. masked lists the bits the umask turns off. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/umask-mode

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": {
      "umask": "<umask>"
    },
    "name": "umask_mode"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No		file
`umask`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and open-world. The description adds meaningful behavioral context beyond annotations: pricing ('$0.001 USDC per successful call'), x402/Solana payment, and an alternate HTTPS GET endpoint, though it does not cover error or rate-limit behavior.

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 front-loaded with the concept and calculation before payment and endpoint details. It is mostly compact, though the sentence about `masked` is terse and the payment/endpoint information is packed into the same paragraph.

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 calculator, the description supplies the core rule, examples, and access/payment details. With no output schema, however, it only partially describes the return shape by mentioning `masked` and implying mode numbers, and it leaves umask format constraints unspecified.

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 carry parameter meaning. It explains the `umask` concept and gives an example value, and implies `kind` selects file versus directory, but it does not spell out accepted umask syntax, format constraints, or the max length.

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 opens with a specific resource and operation: computing the mode of a file or directory under a umask. Concrete examples ('022 makes a file 644 and a directory 755') make the calculation clear, though it does not explicitly distinguish itself from siblings like file_mode or chmod_apply.

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?

There is no explicit when-to-use/when-not guidance or named alternative tool. The intended use is implied by the opening explanation and examples, but an agent must infer when this tool is preferable to related permission/mode tools.

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?