Skip to main content
Glama

ics_parse

Read-only

Parse iCalendar (ICS) text or a public .ics URL. Returns VEVENTs (summary, start/end in UTC/ISO, location) with RRULE expanded to at most 50 occurrences in a bounded window. Data is not stored. Price: 0.003 USDC per call (x402, Base).

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": "ics_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
icsNoRaw ICS text
urlNo
fromNo
textNo
max_occurrencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds several traits the annotations cannot express: recurrence expansion is bounded (max 50 occurrences in a bounded window), data is not persisted, and each call costs 0.003 USDC via x402 on Base. The cost and no-storage disclosures are exactly the kind of behavioral context an agent needs before invoking a metered, open-world tool.

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?

Three tightly packed sentences, front-loaded with purpose then return shape then constraints and cost. Every sentence carries information, though the pricing/x402 clause is the least essential and could be trimmed for a pure capability read.

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 tool with no output schema and low parameter coverage, the description covers the return shape, the recurrence-expansion limit, the statelessness, and the billing model. The remaining gap is input selection among ics/text/url and the fact that no parameter is marked required, which the description should have clarified.

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 coverage is only 17% (just the `ics` field is documented), so the description has to compensate and partially does: 'bounded window' maps to `from`/`to` and 'at most 50 occurrences' maps to `max_occurrences`. However, it never disambiguates the three input channels (`ics` vs `text` vs `url`), nor explains which one is expected, leaving the highest-risk ambiguity in a 6-parameter schema unresolved.

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?

The description opens with a specific verb+resource pair ('Parse iCalendar (ICS) text or a public .ics URL') and then names the exact return payload (VEVENTs with summary, start/end in UTC/ISO, location). No sibling tool in the catalog touches calendars, so there is no ambiguity to resolve; an agent knows immediately what this does.

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 only implied: the phrase 'public .ics URL' signals that non-public/authenticated calendars are out of scope, and the RRULE cap hints at the intended use case (listing occurrences, not full-fidelity export). There is no explicit when-to-use/when-not guidance and no statement that at least one of ics/url/text must be supplied, which matters because the schema lists zero required parameters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources