Place to Be

Find events

search_events

Read-only

Find the events worth going to in a city, a country or worldwide, ranked by how big a moment each is (a 0-100 score from expected crowd and timing) or by start time, optionally only those matching a name (an artist, team, show or venue). Covers concerts, sport, festivals, nightlife, culture and city moments, merged from ticketing, sports and open-data feeds and refreshed daily. Use it for questions like "what's on in Lisbon this weekend", "biggest concerts in London this week", "when are Arsenal at home" or "is Coldplay playing in Europe". Each result has the local date and time, venue, score with a one-line reason, and a link to the event's page.

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

Input Schema

Name	Required	Description	Default
`city`	No	City name in English, e.g. "London", "New York", "Mexico City". Add the country after a comma when a name is shared ("Paris, France"). Omit city and country for worldwide. For the major cities, results also include the big events just outside the city line (SoFi Stadium in Inglewood for Los Angeles, MetLife Stadium for New York); each result names its own town.
`sort`	No	biggest: highest score first. soonest: earliest start first.	biggest
`when`	No	now: on right now. tonight: the rest of today, local time. this_weekend: Friday 17:00 to Sunday night, local time. this_week: the next 7 days. upcoming: the next 160 days.	upcoming
`limit`	No	How many events, 1 to 25.
`query`	No	Only events whose title or venue contains this text: an artist, team, show or venue name, e.g. "Coldplay", "Arsenal", "Madison Square Garden". At least 2 characters.
`country`	No	A whole country instead of one city: English name or ISO 3166-1 alpha-2 code ("Netherlands", "NL"). Ignored when city is given.
`categories`	No	Only these kinds of events. Omit for all.

Output Schema

Name	Required	Description
`sort`	Yes
`when`	Yes
`count`	Yes
`query`	Yes	The name filter, when one was given.
`scope`	Yes	Where: a city, a country, or 'worldwide'.
`events`	Yes
`board_url`	Yes	The live board for this place on placetobe.cc.
`attribution`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

changedInput schema / properties / city / description

Previous value: -"City name in English, e.g. \"London\", \"New York\", \"Mexico City\". Add the country after a comma when a name is shared (\"Paris, France\"). Omit city and country for worldwide."New value: +"City name in English, e.g. \"London\", \"New York\", \"Mexico City\". Add the country after a comma when a name is shared (\"Paris, France\"). Omit city and country for worldwide. For the major cities, results also include the big events just outside the city line (SoFi Stadium in Inglewood for Los Angeles, MetLife Stadium for New York); each result names its own town."

First observedSep 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, it discloses data provenance (ticketing, sports, open-data feeds), refresh cadence (daily), ranking logic (0-100 score from expected crowd and timing), and result contents. This adds substantial behavioral context for an agent deciding whether results are suitable.

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?

The description is front-loaded with the core capability, scope, and ranking, then supports it with examples and result details. It is somewhat long, but each sentence adds useful selection context rather than restating the schema.

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?

Given full schema coverage, read-only annotations, and an output schema, the description supplies everything an agent needs: purpose, ranking modes, temporal and geographic scope, examples, data freshness, and expected result contents. No important gap remains.

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 100%, so every parameter is already well documented in the schema. The description reinforces the ranking and name-matching concepts but does not add syntax or constraints beyond what the schema provides, so the baseline of 3 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 states a specific verb and resource (find events), its geographic scope (city, country, worldwide), ranking modes, and optional name filtering. It clearly positions the tool as a broad event search distinct from the single-event and city-list siblings.

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?

It gives concrete example questions such as 'what's on in Lisbon this weekend' and 'when are Arsenal at home', making the intended usage clear. It does not explicitly name alternatives like get_event or list_cities, so it stops short of full when-not/alternative guidance.

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

All Place to Be 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?