Skip to main content
Glama

Events

events
Read-onlyIdempotent

Reviewed upcoming events (America/New_York times), each with the organizer's official page as source_url. Filter by town, date range and words.

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

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD
fromNoYYYY-MM-DD, default today
townNoTown or county, e.g. "Hornell", "Watkins Glen", "Steuben County"
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add context — which it does by declaring the timezone of returned times, that listings are "reviewed," and that each carries an official organizer page as source_url. It does not mention ordering or how pagination beyond limit works.

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?

Two short sentences, front-loaded with what the tool returns before how to filter. Every clause carries information; only "Reviewed" is slightly ambiguous in placement.

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 read-only list tool whose safety profile is fully covered by annotations and which has no output schema, the description supplies the key missing pieces: timezone, provenance of each record, and the filter dimensions. Sorting and total-count behavior are the only meaningful omissions.

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?

With 60% schema coverage, the schema already documents to, from and town. The description usefully clarifies that "words" maps to the otherwise-undocumented query parameter and that from/to form a date range, but the limit parameter is left entirely to its schema constraints.

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?

"Upcoming events" names a concrete resource with a clear scope (upcoming, reviewed, localized to America/New_York), and the mention of source_url signals it returns organizer-verified listings. It is distinguishable from siblings like news or conditions, though no sibling is named explicitly.

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?

"Filter by town, date range and words" implies how to narrow results, but there is no explicit statement of when to pick this tool over news or get_town, and no exclusions or prerequisites. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources