Skip to main content
Glama

FabTally Utility Belt

by io.github.zvmzaretsky

iCal RRULE -> next N occurrences (paid $0.001)

rrule

PAID $0.001. Expand an iCal RRULE (RFC 5545) recurrence into its next N occurrences. Args: rrule (e.g. 'FREQ=WEEKLY;BYDAY=MO,WE;COUNT=10'), after (ISO, default now), count (default 5), timezone. Tip: include DTSTART for anchored series. Without payment returns the x402 challenge; pass x_payment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoReturn occurrences after this ISO datetime (default now).
countNoHow many occurrences (1-366, default 5).
rruleYesRRULE string, optionally with a DTSTART line.
timezoneNoRender occurrences in this IANA zone.
x_paymentNox402 payment payload (base64) for this PAID tool. If supplied it is forwarded as the X-PAYMENT header to settle the $0.001 call and return the real result instead of a 402 challenge. Omit to get the price challenge first.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description fully discloses the key behavioral trait: this is a PAID tool requiring an x402 payment, and without payment it returns a 402 challenge. It also notes default values for 'after' and 'count', and the timezone handling.

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 efficient, covering payment, purpose, parameters, and a tip in a compact format. Front-loads the PAID indicator. Slightly long but every sentence adds useful information.

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?

Given the tool's complexity (5 params, payment flow, no output schema), the description covers the essential context: what it does, default behavior, payment mechanism, and a usage tip. It does not specify the output format, but the phrase 'next N occurrences' adequately communicates the result.

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 baseline is 3. The description adds value beyond the schema by showing an example RRULE string, explaining the x_payment forwarding behavior, and offering a tip about DTSTART. This enriches parameter understanding.

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 uses a specific verb ('expand') and resource ('iCal RRULE (RFC 5545) recurrence') and defines the output ('next N occurrences'). It clearly distinguishes itself from sibling tools like cron or datemath by focusing on recurrence expansion.

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?

Provides practical guidance: a tip to include DTSTART for anchored series, and explicit instruction on handling the x402 payment challenge ('pass x_payment'). However, it does not explicitly contrast with alternative tools or state when not to use it.

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

All FabTally Utility Belt toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct operation: unit conversion, cron parsing, currency conversion, date math, diff, encoding, hashing, ID generation, JSON schema validation, regex, RRULE expansion, text transforms, and timezone conversion. Even related tools like convert, currency, and timezone are clearly separated by domain, with descriptions that eliminate ambiguity.

Naming Consistency5/5

All tool names are lowercase single-word identifiers without separators or camelCase, forming a clean and predictable pattern. While some are verbs (convert, diff, encode) and others nouns (cron, currency, id), the uniform naming style ensures consistency.

Tool Count5/5

13 tools is well-scoped for a general-purpose utility belt. Each tool covers a common utility without redundancy, fitting comfortably within the ideal 3-15 range.

Completeness5/5

The tool surface covers a broad range of utilities: unit and currency conversion, date/time handling (datemath, timezone, cron, rrule), text processing (text, encode, regex, diff), cryptography (hash), ID generation, and schema validation. No obvious gaps exist for the stated purpose.

Resources