ScorpTech x402 Tools

Timecode Frames

timecode_frames

Read-onlyIdempotent

Count the frames in an SMPTE timecode from midnight. Rates are 24, 25 and 30. A colon is non-drop and a semicolon is drop-frame, which is only legal at 30. Drop-frame skips 00 and 01 at the start of each minute except every tenth minute, so 01:00:00;00 is frame 107892 rather than 108000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/timecode-frames

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>"
    },
    "name": "timecode_frames"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive behavior, yet the description still adds substantial context: it discloses per-call pricing, the x402/Solana payment requirement, and an alternate HTTPS endpoint. It also explains drop-frame legality and the exact frame arithmetic, which is behavioral detail not present in annotations.

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 core operation is front-loaded in the first sentence, followed by precise rules and a concrete worked example. The pricing and URL lines add real value for an agent, so they earn their place, though the block is somewhat dense.

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?

With no output schema and zero schema descriptions, the description supplies the missing semantics: valid rates, drop-frame rules, and even a sample result (01:00:00;00 = frame 107892). It stops short of stating the return type explicitly, but a frame count is strongly implied by the verb 'count'.

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?

Schema coverage is 0%, so the description must compensate, and it does: it defines the timecode format semantics (colon = non-drop, semicolon = drop-frame) and constrains rates to 24/25/30 while noting drop-frame is legal only at 30. It does not explicitly map these clauses to the parameter names, but the meaning is clear.

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?

States a specific verb and resource ('Count the frames in an SMPTE timecode from midnight') and immediately scopes the rate domain. It does not distinguish itself from the sibling frames_timecode, which appears to be the inverse operation, leaving the agent to infer directionality.

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?

Usage is implied by the conversion nature and the rate/drop-frame rules, but there is no explicit statement of when to pick this over frames_timecode or timecode_diff. No prerequisites or exclusions are given beyond the semicolon-only-at-30 constraint.

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?