ScorpTech x402 API

Duration Parse

duration_parse

Read-onlyIdempotent

Parse any duration into seconds and every common format: ISO 8601 (P1DT2H30M, PT1.5S, P2W), clock (1:02:03.5, 02:30), Go / compact (1h30m, 2d4h), and plain English ("an hour and a half", "2.5 days", "3 weeks ago", "90 secs"). Returns total seconds / milliseconds / minutes / hours / days, normalised ISO 8601, H:MM:SS, compact and human text, and flags month / year approximations. Up to 50 inputs per call. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/duration-parse

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "duration_parse"
  }
}

Input Schema

Name	Required	Description	Default
`input`	No	Duration text
`inputs`	No	Batch of durations (instead of input)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, but the description adds genuinely new behavioral facts: a $0.001 USDC x402/Solana charge per successful call, a 50-input batch ceiling, and full disclosure of the returned fields plus month/year approximation flags. It stops short of stating what happens on unparseable input (error vs silent fallback), which is the remaining behavioral gap.

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?

Front-loaded with accepted formats, then outputs, then the batch cap and pricing. Every sentence carries information; the HTTPS endpoint sentence is the only marginally optional element, but it serves agents without MCP transport.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description enumerates every return field (seconds/ms/minutes/hours/days, normalised ISO 8601, H:MM:SS, compact, human text) as well as approximation flags, batch limits and cost. Nothing an agent needs in order to call it correctly is missing.

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 100%, so a 3 would be the baseline, but the description expands the bare 'Duration text' schema label into a taxonomy of accepted grammars and notes that batching is the 'inputs' path. This adds real meaning beyond the schema's type and maxLength constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (parse) and resource (duration) and enumerates the exact input families it accepts with concrete examples: ISO 8601, clock, Go/compact, plain English. An agent immediately knows whether a given string belongs to this tool rather than to a sibling like timecode_duration or unit_convert.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear implied usage plus concrete operational guidance: single 'input' vs up to 50 in a batch, and that the same function is reachable over HTTPS. It does not explicitly exclude related tools (unit_convert, timestamp_convert, timecode_duration), so sibling disambiguation is left 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?