ScorpTech x402 API

Rrule Expand

rrule_expand

Read-onlyIdempotent

Expand an iCalendar RFC 5545 RRULE (recurring event rule, as used by Google Calendar, Outlook, CalDAV) into concrete occurrences in any IANA zone, DST-correct, with an English description. Supports FREQ (yearly … secondly), INTERVAL, COUNT, UNTIL, BYMONTH, BYWEEKNO, BYYEARDAY, BYMONTHDAY, BYDAY with ordinals (2MO, -1FR), BYHOUR / BYMINUTE / BYSECOND, BYSETPOS, WKST, plus EXDATE / RDATE and an after / before window. Accepts a bare rule or full DTSTART + RRULE lines. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/rrule-expand

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": {
      "rrule": "<rrule>"
    },
    "name": "rrule_expand"
  }
}

Input Schema

Name	Required	Description	Default
`tz`	No		UTC
`after`	No	Only occurrences at or after this time
`limit`	No	Max occurrences to return
`rdate`	No	Extra occurrences
`rrule`	Yes	RRULE value, optionally with DTSTART / RRULE / EXDATE / RDATE lines
`before`	No	Only occurrences at or before this time
`exdate`	No	Excluded occurrences (local date-times or dates)
`dtstart`	No	First occurrence (ISO 8601 local time in tz); overrides a DTSTART line

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.7/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, and open-world behavior. The description adds useful context: DST correctness, supported RRULE components, accepted input forms, pricing, and an HTTPS endpoint. It still lacks details on response shape or payment failure 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 dense but front-loaded: it defines the tool, lists supported features, then covers input format, pricing, and endpoint. The long RRULE feature list is relevant, though it could be slightly tighter.

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?

For a fairly complex RRULE expansion tool, the description covers the key inputs, timezone and DST behavior, supported recurrence components, pricing, and endpoint. Since there is no output schema, it only broadly implies return values via 'concrete occurrences' and 'English description,' leaving some response-shape detail unstated.

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 high at 88%, so the schema already documents most parameters. The description adds meaning for rrule input formats, tz, exdate/rdate, and after/before filtering, but it does not expand much on limit or other parameter semantics beyond what the schema provides.

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: expand an iCalendar RFC 5545 RRULE into concrete occurrences. It clearly explains the domain and distinguishes the operation conceptually, though it does not explicitly contrast with sibling tools such as ics_parse or cron_explain.

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 use case is clear from the description, including timezone, DST handling, and after/before windows. However, it does not say when to use this tool instead of related siblings like ics_parse, ics_generate, or cron_explain, and it provides no exclusions.

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?