Skip to main content
Glama
chrischall

onthecheap-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Overview of a city’s events across a month

otc_events_month_overview
Read-onlyIdempotent

Scan a city's month at a glance: get day-by-day previews of events with true daily counts. Identify the busiest days, then query a specific date for the full schedule.

Instructions

Day-by-day overview of a whole month from an "on the Cheap" city’s events calendar: for each day, the true number of listings and a short preview of them. Pass the site key for the city (see otc_list_sites). The calendar shows at most four listings per day, so events is a preview while total is the real count — call otc_list_events for a specific date to get that day's complete schedule. The national hub has no local calendar and is not a valid site here. Use this to find the busiest days or scan a month at a glance. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesWhich "on the Cheap" city to read. Required — there is no default site. One of: charlotte, denver, atlanta, chicago, columbus, seattle, kansascity, miami, orlando, portland, richmond, southernmaine, triangle, national. Common aliases also work (milehigh, raleigh, rva, southflorida, kc, …). Use otc_list_sites for the full list with the area each one covers.
monthNoMonth to summarise, as ISO YYYY-MM. Defaults to the current month in the city’s own time zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • changedInput schema / properties / month / description
      Previous value: -"Month to summarise, as ISO YYYY-MM. Defaults to the current month."New value: +"Month to summarise, as ISO YYYY-MM. Defaults to the current month in the city’s own time zone."
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Even with readOnlyHint/openWorldHint/idempotentHint annotations, the description adds crucial behavioral context: 'The calendar shows at most four listings per day, so events is a preview while total is the real count'. It discloses the preview limitation, the invalid national hub, and month default behavior, going well 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.

Conciseness5/5

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

The description is front-loaded with the core purpose, and every subsequent sentence adds distinct value: preview vs. total, alternative tool, invalid site, use cases, and read-only confirmation. It is slightly longer than average but contains zero filler; every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no output schema, the description is remarkably complete: it explains the main return fields (events vs total), the four-listing cap, the month default, invalid site values, and the alternative tool for full schedules. An agent has everything needed to invoke it correctly.

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 the baseline is 3. The description adds value on top by telling the agent to pass the site key, referencing otc_list_sites, and explicitly stating the national hub is not valid. Month semantics are fully covered by the schema, so a modest bump to 4 is appropriate.

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 opens with a specific verb+resource: 'Day-by-day overview of a whole month' and clearly states the output concept ('true number of listings and a short preview'). It distinguishes itself from siblings by naming otc_list_events (for complete daily schedules) and otc_list_sites (for city keys), so an agent knows exactly what this tool does and does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: 'Use this to find the busiest days or scan a month at a glance,' and directs the agent to otc_list_events for a specific date's complete schedule. It also warns that the national hub is not a valid site, and points to otc_list_sites for key lookup — clear routing versus alternatives.

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