Skip to main content
Glama

Boston Calendar

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Events

events
Read-onlyIdempotent

Upcoming Greater Boston events from The Boston Calendar. Defaults to a 2-week window from today. Filter by date range, keyword (title/description/tags), and free admission. Returns normalized events sorted by date/time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest event date YYYY-MM-DD (default: 14 days from `from`). Pass "" for no upper bound.
fromNoEarliest event date YYYY-MM-DD (default: today).
limitNoMax events to return (1-200, default 50).
queryNoKeyword filter over title, description, and tags, e.g. "free music", "kids", "art".
free_onlyNoIf true, only events whose admission is free.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "music"
+  },
+  {
+    "free_only": true,
+    "from": "2025-01-15",
+    "limit": 30,
+    "query": "kids",
+    "to": "2025-02-15"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, non-destructive, and idempotent, so the description's additional details about default 2-week window, normalization, and sorting by date/time provide useful behavioral context beyond the structured metadata.

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 three sentences, front-loaded with the core purpose, and every sentence adds value: source, default window, filters, and output format. No filler or redundancy.

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 simplicity, a read-only event lookup with a full schema and annotations, the description covers the essential context: source, default window, filters, and output sort. It lacks explicit mention of pagination or result size defaults, but the schema's limit parameter covers that, so 4 is appropriate.

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?

The input schema already covers 100% of the parameters with descriptive details (e.g., 'Keyword filter over title, description, and tags'), so the description adds little beyond what the schema documents. It mentions the same filter categories but no new semantic information.

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 clearly states the tool's function: it returns upcoming Greater Boston events from The Boston Calendar. It specifies the resource (events), source (Boston Calendar), and default behavior (2-week window). This distinguishes it from other tools, none of which are event-related.

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 description implicitly provides usage context: it lists the available filters (date range, keyword, free admission) and the default date window, making it clear when to use this tool. No explicit alternatives are given, but the sibling list contains no comparable event tool, so exclusions aren't necessary.

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

All Boston Calendar toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources