Skip to main content
Glama
Sign In
Philly Events MCP Server

Philly Events MCP Server

by anewt225
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Generate Weekly Event Digest

philly_weekly_digest
Read-onlyIdempotent

Generate a weekly digest of Philadelphia events for the next 7 days, organized by category with filters for neighborhoods, categories, free events, and result limits.

Instructions

Generate a curated weekly digest of Philadelphia events.

This tool searches for events happening in the next 7 days and formats them as a digestible newsletter-style summary, organized by category.

Args:

  • categories (array, optional): Focus on specific categories

  • neighborhoods (array, optional): Focus on specific neighborhoods

  • include_free_only (boolean): Only include free events (default: false)

  • max_events (number): Maximum events in digest (default: 20, max: 50)

  • response_format ('markdown' | 'json'): Output format

Perfect for:

  • Weekly event roundup emails

  • Planning your weekend

  • Discovering new things to do

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

Input Schema

NameRequiredDescriptionDefault
categoriesNoFilter digest by categories of interest
max_eventsNoMaximum events to include in digest
neighborhoodsNoFilter digest by preferred neighborhoods
response_formatNomarkdown
include_free_onlyNoOnly include free events

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false. The description adds the 7-day search window and the output shape (newsletter-style summary organized by category), which is useful operational context beyond the annotations.

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

Conciseness3/5

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

The purpose and use-case sections are front-loaded and clear, but the Args block duplicates parameter information already present in the schema, so not every line earns its place.

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 5-optional-parameter tool with no output schema, the description explains the return format (newsletter-style summary organized by category) and the temporal scope. It lacks routing guidance versus siblings, but otherwise gives enough to call the tool correctly.

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 80%, so the baseline is 3. The Args section largely repeats schema descriptions and even omits the min=5 constraint on max_events and the default 'markdown' for response_format, so it adds little beyond the structured schema.

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?

States a specific verb 'Generate' and resource 'curated weekly digest of Philadelphia events', and clarifies it searches the next 7 days and formats a newsletter-style summary. The digest framing distinguishes it functionally from search siblings, but it does not name an alternative tool explicitly.

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 clear use cases ('Perfect for: Weekly event roundup emails, Planning your weekend...') and a temporal context (next 7 days). It does not state when to prefer it over siblings such as philly_search_events or philly_export_to_calendar, nor any 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