Skip to main content
Glama

list_events

Read-onlyIdempotent

List events in the approved business with ticket capacity and allocated places. Filter by published to find drafts or public events. Use from and to in Unix milliseconds to find overlapping events.

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
toNo
fromNo
offsetNo
publishedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: from/to select events that *overlap* the range rather than being contained by it, and 'published' partitions drafts from public events. It omits pagination behavior and any note on the unbounded default result set, which keeps it from 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?

Three short sentences, each earning its place: purpose and payload first, then the published filter, then the date-range semantics. No filler and no repetition of the tool name or annotations.

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?

With four optional parameters, an output schema absent, and annotations covering safety, the description supplies the essential semantics an agent needs to call it correctly. The remaining gaps are the undocumented `offset` parameter and no hint about result size or pagination, which are moderate for a list tool.

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 semantics, and it does for three of four parameters: `published` (drafts vs public), `from`/`to` (Unix milliseconds, overlap semantics). `offset` is never mentioned, and the schema's maximum bounds on from/to go unexplained, so it is not fully compensating.

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 opens with a specific verb+resource ('List events') and adds scope ('in the approved business') plus the payload ('ticket capacity and allocated places'), so an agent knows what it returns. It does not explicitly distinguish itself from resource-specific siblings like list_event_attendees, but the resource boundary is clear from the name and opening clause.

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 gives concrete filter guidance ('Filter by published to find drafts or public events') and an intended use for the date range ('find overlapping events'), which implies when to use it. It stops short of naming when not to use it or pointing to an alternative tool for a different need, so guidance is implicit 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