Skip to main content
Glama

Search Events

search_events
Read-only

Search upcoming public events, activities and meetups on Moments in one city. Filter by time window, category, free entry or a text query. Returns event titles, times, venues, prices and the event page URL. Event texts come from third-party organizers. Data is public Moments event listings for Norwegian and other cities. Event texts come from third-party organizers.

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

Input Schema

NameRequiredDescriptionDefault
cityYesCity slug, for example oslo. Use list_cities for the full list.
freeNoOnly free events.
whenNoTime window: i-dag (today), i-morgen (tomorrow), helgen (this weekend), denne-uken (this week), neste-uke (next week), gratis (free events). Omit for all upcoming.
limitNo
queryNoFree-text search, for example jazz or quiz.
categoryNoCategory: musikk (music), kultur (culture), mat (food), sport, sosialt (social), workshops, gaming.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add real value by disclosing the return contents (titles, times, venues, prices, URLs) and that event text originates from third-party organizers, which is useful trust context. It stops short of covering pagination or result-count behavior, so a 3 rather than higher.

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 opening sentence is front-loaded with purpose and filters, and the return summary follows logically. However, 'Event texts come from third-party organizers' is duplicated verbatim at the end, and the provenance sentence overlaps with the 'Data is public Moments event listings' sentence — clear waste in a short description.

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 search tool with no output schema, the description explains what comes back and where the data originates, which is what an agent needs to call and trust it. Missing only operational details like the default limit of 10 and max of 20, which the schema already supplies.

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?

With 83% schema coverage and three enums already documented inline, the schema carries most of the burden. The description reinforces the city-scoping constraint and the filter categories without adding syntax detail, which is adequate but not additive; the baseline-3-plus margin reflects that the 'one city' scoping clarifies the required param's role.

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?

The description names a specific verb and resource ('Search upcoming public events, activities and meetups') and scopes it to 'one city' with a named source (Moments). It does not explicitly distinguish itself from the siblings get_event or list_cities, leaving that routing to the schema note in the city param, so it falls short of a 5.

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?

It lists the available filter dimensions (time window, category, free entry, text query), which implies the discovery use case, but never states when to choose this over get_event for a single event or list_cities for the city list. Usage is inferable rather than explicit.

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