Skip to main content
Glama

Discover events

discover_events
Read-only

Search FeedIRL for upcoming real-world events and experiences by location, date window, budget, and interests/vibe. Returns ranked results with a one-line reason, local start time when known, price when available, source, referral ticket link, and last-verified timestamp. Discovery only — send people to referral_url; FeedIRL does not book or charge.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lngNo
cityNoCity or metro name
dateNoYYYY-MM-DD start
limitNo
budgetNoMax price in USD
end_dateNoYYYY-MM-DD end
interestsNoComma-separated interests / vibe (comedy, live music, …)
radius_miNo
ai_providerNo
include_adultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, destructiveHint=false), and the description adds meaningful context beyond them: ranked results, a per-result reason, local start time, price, source, referral ticket link, and a last-verified timestamp. It does not address pagination behavior for the limit parameter, how stale results are handled, or rate limits.

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 tightly written sentences: the first front-loads capability and filters, the second front-loads the return payload and then the usage boundary. Every clause carries information; nothing is redundant or restated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description compensates well for the absent output schema by describing the result shape, and it clarifies the no-booking scope. However, with 11 optional parameters and zero required, an agent gets no guidance on default behavior when filters are omitted, nor on what include_adult or ai_provider control — a real gap for a tool with open-world search semantics.

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 coverage is 45% (below half), so the description needs to compensate, and it partially does by naming the filter families that map to lat/lng/city, date/end_date, budget, and interests. It says nothing about limit, radius_mi, ai_provider, or include_adult, and adds no syntax or format detail beyond what the schema already documents.

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 opens with a specific verb and resource ('Search FeedIRL for upcoming real-world events and experiences') and enumerates the filter dimensions (location, date window, budget, interests/vibe). With no sibling tools to disambiguate against, this leaves no ambiguity about what the tool does.

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 closing sentence establishes a clear boundary — 'Discovery only — send people to referral_url; FeedIRL does not book or charge' — which tells the agent this is not a booking/purchase tool. It stops short of naming an alternative tool or stating required preconditions (e.g., that no parameters are required, or when to prefer lat/lng over city).

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