ScorpTech x402 API

Timecode Add

timecode_add

Read-onlyIdempotent

Add a signed frame count to a timecode and stay inside the same day. A result before midnight or at the next midnight is rejected. The semicolon, if present, keeps the result in drop-frame. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/timecode-add

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": {
      "code": "<code>",
      "add": "<add>"
    },
    "name": "timecode_add"
  }
}

Input Schema

Name	Required	Description	Default
`add`	Yes
`code`	Yes
`rate`	No

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?

Beyond annotations (readOnlyHint, idempotentHint, openWorldHint, destructiveHint), the description adds valuable behavioral context: the day-boundary constraint, drop-frame preservation via semicolon, pricing ($0.001 USDC per call via x402 on Solana), and an alternative HTTPS endpoint. It does not discuss rate limits or output format, but the added details are substantial.

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 core operation, followed by constraints, drop-frame behavior, pricing, and an alternative endpoint. Every sentence adds relevant information without waste, though the pricing and URL could be separated for clarity.

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?

Given three parameters with no schema descriptions and no output schema, the description covers the main arithmetic and day-boundary constraints but omits the 'rate' parameter and does not explicitly state the return value (e.g., a timecode string). The annotations cover safety, but operation semantics remain incomplete.

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?

With 0% schema description coverage, the description compensates for two key parameters: 'add' is clarified as a 'signed frame count' and 'code' as a timecode with optional semicolon for drop-frame. The 'rate' parameter (enum 24/25/30, default 30) is not mentioned at all, leaving its semantics partially undocumented.

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 states a specific verb (add) and resource (timecode) with a clear operand (signed frame count), making it distinct from siblings like timecode_diff or timecode_frames. However, it does not explicitly name or contrast any sibling tool, so it falls short of full sibling differentiation.

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?

The description implies when to use the tool by describing its operation and constraints (e.g., 'stay inside the same day', 'A result before midnight ... is rejected'). There is no explicit guidance on when to use versus alternatives or when not to use it, leaving usage to inference.

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?