Skip to main content
Glama

Discover Events

discover_events
Read-onlyIdempotent

Find public upcoming events on SocialLoop — answer "what's on in San Francisco this weekend" or "any free tech meetups next month". Each result carries the event name, start/end time with timezone, city, address and venue (only a public locationArea when the host keeps the exact location for registered guests), category, host, ticket price range, and the page to RSVP or buy on. Searches the next 365 days by default. Filters: city, date_from, date_to, free_only, limit, offset (pass the returned nextOffset to page through every result). Only public events — never a private, members-only, draft or cancelled one. No login or account required. Read-only.

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
cityNo
limitNo
offsetNo
date_toNo
date_fromNo
free_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "maximum": 299,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real behavior: no login or account required, public-only visibility rules, a 365-day default window, and the nextOffset paging contract. It also discloses the privacy nuance that exact venue is withheld in favor of a public locationArea when the host restricts it.

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?

Front-loaded with purpose and example queries, then return fields, then filters and paging — a sensible order with no filler sentences. The return-field enumeration is long, but it substitutes for the absent output schema, so it earns its space.

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?

With no output schema, the description compensates by enumerating every returned field (name, times with timezone, city, address/venue, category, host, price range, RSVP page). Combined with auth, visibility, default range, and paging details, an agent has everything needed to call and interpret results.

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 description coverage is 0%, so the description must carry the load, and it names all six filters and explains offset paging via the returned nextOffset. It omits the date-time format expected by date_from/date_to and the limit/offset caps (50 and 299), which the schema enforces but never explains.

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?

Opens with a specific verb and resource ("Find public upcoming events on SocialLoop") and immediately scopes it with two natural-language example queries. The public-only constraint ("never a private, members-only, draft or cancelled one") separates it from the sibling list_events/list_shared_events family without needing to name them.

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?

Gives concrete when-to-use framing via the example questions and states the default 365-day search window, so an agent knows it can call with zero arguments. It does not name an alternative tool or state when NOT to use this one, which keeps it short of a 5.

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.