Skip to main content
Glama

Search events

search_events
Read-onlyIdempotent

Find live events on shapargullay (Pakistan): by words, city, category, when and price. Returns upcoming events soonest first with their page links for booking.

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

NameRequiredDescriptionDefault
cityNoA Pakistani city, e.g. Lahore, Karachi, Islamabad. Use list_cities for the cities with events.
whenNoA time window in Pakistan time.
limitNoHow many events to return, 1 to 25. Default 10.
queryNoWords to match: performer, event name, venue, organizer or theme, e.g. "qawwali", "Zaryab Malik", "stand-up".
date_toNoYYYY-MM-DD (Pakistan time), inclusive.
categoryNoconcerts, qawwali, comedy, theatre, workshops, food, kids, festivals, art, online.
date_fromNoYYYY-MM-DD (Pakistan time), inclusive.
free_onlyNoOnly free events (no ticket price).
online_onlyNoOnly online events (joined by link, no venue).
max_price_pkrNoCheapest ticket at most this many rupees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / free_only / description
      Added value: +"Only free events (no ticket price)."
    • changedInput schema / properties / limit / description
      Previous value: -"Default 10."New value: +"How many events to return, 1 to 25. Default 10."
    • addedInput schema / properties / online_only / description
      Added value: +"Only online events (joined by link, no venue)."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: results are upcoming-only, ordered soonest first, and each carries a booking page link. It does not mention pagination limits, empty-result behavior, or default result count (that is in the schema), so it stops short of a 5.

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 sentences, zero filler. The searchable facets come first and the return behavior second, so the most decision-relevant information 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 10-parameter, all-optional search tool the description is nearly sufficient: it names the domain, the facets, and the return ordering plus links. Absent an output schema, it partially compensates by describing results, though it says nothing about empty results or how many fields each event carries.

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 all ten parameters are already documented with examples and formats. The description only recaps the facet list (words, city, category, when, price) and omits the boolean filters and date range; it adds no syntax or semantics beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Find live events on shapargullay (Pakistan)') and enumerates the searchable facets: words, city, category, when, price. It also describes the result shape (upcoming events, soonest first, with booking page links), which lets an agent distinguish it from get_event without opening a schema.

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?

Usage is implied by 'Find ... by words, city, category, when and price', which sketches the search use case, but the description never states when to prefer this over siblings such as get_event, list_categories, or list_cities, nor any exclusions. The only routing hint ('Use list_cities for the cities with events') lives in the city parameter schema, not the description.

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