events

get_city_events

Top upcoming events in a city (overall plus sports and concerts breakdowns). Use city slugs from get_top_cities, e.g. "austin-texas".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city_slug": "<city_slug>"
    },
    "name": "get_city_events"
  }
}

Input Schema

Name	Required	Description	Default
`city_slug`	Yes	City slug, e.g. "las-vegas-nevada"

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses that results are 'top upcoming events' with breakdowns, implying a read-only operation, but it does not explicitly state read-only behavior, data ordering, or any limitations. The absence of annotation means a 3 is appropriate for partial context.

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?

Two concise sentences deliver the core purpose and the key usage instruction. Every word is useful, no redundancy, and the content is front-loaded.

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 single-parameter tool with no output schema, the description adequately covers what is returned (overall plus breakdowns) and how to obtain the input. It could mention result count or sorting, but overall it is sufficiently complete for a simple tool.

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% and the schema already describes the city_slug parameter. The description adds value by telling agents to use slugs from get_top_cities and gives an example ('austin-texas'), enriching the schema's basic example ('las-vegas-nevada'). This exceeds the baseline of 3.

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 returns 'top upcoming events in a city' with distinct breakdowns (overall, sports, concerts), which is specific and unambiguous. It differentiates from siblings like search_events by focusing on 'top' rather than arbitrary search.

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 explicitly directs users to use city slugs from get_top_cities, providing a prerequisite and example. It does not explicitly mention alternatives or exclusions, but the context is clear enough for a focused tool.

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

All events tools Inspect

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

Need Help?