Skip to main content
Glama

list_event_attendees

Read-onlyIdempotent

List ticket holders and admission status for an event in the approved business.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "list_event_attendees"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/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 safety is covered. The description adds only the tenancy/authorization qualifier 'in the approved business'; it says nothing about result-set size, pagination, or whether results are complete or paged, even though an offset parameter with a 100000 maximum exists.

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?

One front-loaded sentence with no filler, hedging, or redundant restatement of the tool name. Every word carries information; there is nothing to trim.

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

Completeness2/5

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

For a three-parameter listing tool with no output schema and zero schema coverage on descriptions, the definition is too thin. It neither explains the pagination/offset semantics nor describes what an attendee record contains beyond 'admission status', both of which the agent would need to call it confidently.

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%, so the description must carry parameter meaning and largely does not. 'Admission status' loosely gestures at the status enum but never names it or its allowed values (issued, checked_in, voided), and the offset pagination parameter is not mentioned at all, leaving the highest-risk parameter undocumented in prose.

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 states a specific verb and resource: list the ticket holders and admission status for an event. That distinguishes it reasonably from list_events and from the write-side ticket tools (check_in_event_ticket, void_event_ticket), though it does not name any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The only scoping information is 'for an event in the approved business', which implies an event-scoped listing but does not tell the agent which tool to pick when it wants rosters, events, or check-in state.

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