ScorpTech x402 Tools

Ics Generate

ics_generate

Read-onlyIdempotent

Generate a standards-compliant iCalendar (.ics, RFC 5545) file from JSON events — ready for Google Calendar, Outlook and Apple Calendar invites or "add to calendar" links. Time zones with a generated VTIMEZONE (DST rules from the IANA database), all-day and multi-day events, recurrence (RRULE validated, EXDATE), reminders (VALARM), organizer / attendees with RSVP, location, URL, geo, categories and status. Proper escaping and 75-octet line folding; deterministic UIDs. Returns the .ics text and a data: URI. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/ics-generate

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": {
      "events": "<events>"
    },
    "name": "ics_generate"
  }
}

Input Schema

Name	Required	Description	Default
`events`	Yes	Events (max 200): summary, start, end \| durationMinutes, allDay, timezone, description, location, url, uid, rrule, exdates, alarms (minutes before), organizer {name,email}, attendees [{name,email,role,rsvp}], status, categories, geo {lat,lon}, transparent, sequence, priority, class
`method`	No	REQUEST for meeting invitations (needs organizer)	PUBLISH
`timezone`	No	IANA time zone for events without their own (e.g. Europe/Berlin)	UTC
`calendarName`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations, which only declare readOnly/idempotent/non-destructive. It adds the return shape (.ics text plus a data: URI), reinforces idempotency with deterministic UIDs, and discloses the paid access model ($0.002 USDC per successful call via x402 on Solana) plus the equivalent HTTPS endpoint — the kind of auth/cost context an agent must know before calling.

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 correctly: core action first, then feature coverage, then return value, then cost/endpoint. The middle feature enumeration is a long list, but each element (VTIMEZONE, recurrence, alarms, attendees) corresponds to a distinct capability an agent would otherwise have to guess at, so little is wasted.

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?

No output schema exists, and the description compensates by stating the return value explicitly. With 4 parameters, a 200-event cap, a documented payment model, and full feature scope disclosed, an agent has everything needed to decide and call correctly.

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 75% (baseline 3), and the description pushes past it by explaining what the nested event fields actually produce: VTIMEZONE blocks with IANA DST rules, validated RRULE/EXDATE recurrence, VALARM reminders, organizer/attendee RSVP semantics, and proper escaping with 75-octet folding. It adds real meaning about behavior of the parameters rather than just restating field names, though it never clarifies the method/timezone interaction (REQUEST requiring an organizer) beyond what the schema already says.

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+resource (generate an iCalendar .ics) plus the exact standard (RFC 5545) and input source (JSON events). The output framing — Google Calendar, Outlook, Apple Calendar invites or 'add to calendar' links — makes it unmistakably distinct from the inverse sibling ics_parse without the agent needing to open either schema.

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?

Gives clear situational context: producing invites and add-to-calendar links for major calendar clients. It does not explicitly exclude alternatives or name ics_parse / rrule_expand as the tools to use when you need the reverse direction, so exclusions are 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 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?