Skip to main content
Glama

List upcoming Florida events

list_events
Read-onlyIdempotent

Real, sourced events on Quo's calendar (Art Basel, F1 Miami GP, Ultra, etc.), dates, venue, and demand level. Useful for planning a trip around, or timing a ride request against, a specific event.

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

Input Schema

NameRequiredDescriptionDefault
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive, closed-world operation. The description adds useful context that events are 'real, sourced' and that results include dates, venue, and demand level, but it does not disclose date-range behavior, whether only future events are returned, or how category filtering works.

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 front-load what the tool returns and then explain when to use it. The examples earn their place by making the event scope concrete, and there is no redundant wording.

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 simple read-only list tool with only one optional filter and no output schema, the description is largely complete: it covers the source, return fields, and use cases. The main gap is the undisclosed category filter, which an agent would need to infer from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description never mentions the optional 'category' parameter or explains that it filters by enum values such as motorsport, art, music, and yachting. The enum values themselves are readable in the schema, but the description does not compensate for the missing schema documentation as required at low coverage.

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 uses a specific verb and resource ('list' events on Quo's calendar) and names concrete examples (Art Basel, F1 Miami GP, Ultra) plus returned fields (dates, venue, demand level). It is clearly distinguishable from ride, concierge, fleet, and membership 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 explicitly says the tool is useful for planning a trip around an event or timing a ride request against one, giving clear usage contexts. It does not name when-not-to-use cases or point to an alternative sibling, so it falls 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.

Resources