Skip to main content
Glama
Sign In
wallos-mcp

wallos-mcp

by LovelessCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Export the calendar feed

get_ical_feed
Read-only

Generate an iCalendar feed with one all-day event per upcoming payment for calendar subscriptions, providing the raw export instead of a summary.

Instructions

The same calendar feed Wallos serves for subscribing in a calendar app: one all-day event per upcoming payment, as an iCalendar document. Useful when someone wants the raw export rather than a summary.

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

Input Schema

NameRequiredDescriptionDefault
convert_currencyNoConvert prices into the main currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral context about the return shape: an iCalendar document containing one all-day event per upcoming payment, positioned as a raw export rather than a summary.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences, front-loads the core identity and output format, and ends with a clear usage cue. There is no wasted text.

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 simple read-only export with no output schema, the description explains the essential return format and event granularity. It does not cover nuances such as date range or timezone behavior, but the annotations and full schema coverage make it adequate for correct invocation.

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 100%, so the single convert_currency parameter is already documented by the schema. The description does not add any parameter-specific meaning, which matches the baseline of 3 when the schema does the heavy lifting.

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?

The description clearly identifies the resource and output format: the same calendar feed Wallos serves, with one all-day event per upcoming payment, as an iCalendar document. It does not name a sibling tool, but the contrast with 'a summary' gives enough differentiation to understand its role.

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?

It gives an implied use case: 'Useful when someone wants the raw export rather than a summary.' However, it does not explicitly state when to use this tool versus a specific alternative, nor does it mention prerequisites or exclusions.

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

Deploy Server

Other Tools