Skip to main content
Glama
anewt225

Philly Events MCP Server

by anewt225
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Export Events to Calendar Format

philly_export_to_calendar
Read-onlyIdempotent

Export Philadelphia event IDs to Google Calendar JSON for API import. Include event descriptions and source links to add events to your calendar.

Instructions

Convert Philadelphia events to Google Calendar format for import.

This tool takes event IDs (from search results) and returns them in Google Calendar JSON format, ready for import via the Google Calendar API.

Args:

  • event_ids (array): Array of event IDs to export (max 50)

  • include_description (boolean): Include full description (default: true)

  • include_source_link (boolean): Include link to original event (default: true)

Returns: Array of Google Calendar event objects ready for API import.

Example workflow:

  1. Use philly_search_events to find events

  2. Note the event IDs from results

  3. Call this tool with those IDs to get calendar format

  4. Import to Google Calendar via API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idsYesArray of event IDs to export
include_descriptionNoInclude full event description in calendar event
include_source_linkNoInclude link to original event page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description adds the key behavioral boundary that this tool only produces Google Calendar JSON and does not itself push to the API. It also flags the 50-ID cap, though that is duplicated from the schema. Error behavior on invalid IDs is not disclosed.

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?

Purpose is front-loaded in the first sentence and the example workflow is genuinely useful. However, the Args and Returns blocks largely duplicate the schema and the 'ready for import via the Google Calendar API' point is stated twice, so a little trimming would help.

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?

With no output schema, the description correctly explains the return value (array of Google Calendar event objects) and the end-to-end workflow. It is nearly complete for a simple read-only converter, with only edge-case/error handling left unaddressed.

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 baseline is 3. The Args block restates the same parameter descriptions and defaults already present in the schema, adding no new semantics such as ID format or behavior for unknown IDs.

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 and resource ('Convert Philadelphia events to Google Calendar format') and immediately scopes it as a format-conversion step for import, which no sibling tool does. An agent can distinguish it from philly_search_events or philly_weekly_digest without reading any 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?

The example workflow explicitly routes the agent: run philly_search_events first, capture IDs, then call this tool. That names the alternative/prerequisite concretely. It stops short of stating exclusions (e.g., what to do for non-Philadelphia or non-Google targets), so it is clear context rather than full when/when-not guidance.

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