Sonar Connections

See an event's team: co-hosts and door staff (hosts)

event_team_list

Read-onlyIdempotent

Lists the team of an event the signed-in person hosts or co-hosts, as the organizer dashboard's Team panel does: each Co-host and Door staff member with their role, the last four digits of their number, and whether they have joined (signed in) or are still pending. eventIdOrName is the event id or its name as the host says it ("my quince"). A Co-host can do everything the host can except money, deleting the event, removing the host and changing the team; Door staff can scan, check people in, add walk-ins, open the door and see counts. Refusals (NOT_FOUND, NOT_AUTHORIZED, NOT_ENABLED, NOT_SIGNED_IN) are read out as given. It requires a personal connector token.

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": {
      "eventIdOrName": "<eventIdOrName>"
    },
    "name": "event_team_list"
  }
}

Input Schema

Name	Required	Description	Default
`eventIdOrName`	Yes	The event id or the event name as the host says it.

Output Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`rows`	No
`error`	No
`counts`	No
`viewer`	No
`eventId`	No
`message`	No
`servedBy`	No
`canManage`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safe-read profile, and the description adds substantially: the personal connector token requirement, the exact refusal codes surfaced (NOT_FOUND, NOT_AUTHORIZED, NOT_ENABLED, NOT_SIGNED_IN), and the joined-vs-pending distinction. This is rich context beyond what the structured fields provide.

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 the core action and return contents, then constraints and refusals. The sentence describing what Co-hosts and Door staff can do is somewhat tangential to a list operation, but it supplies useful vocabulary for interpreting the returned roles, so it mostly earns its place.

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?

An output schema exists so return values needn't be restated, annotations carry the safety profile, and the description covers auth, refusal modes, and role semantics. An agent has everything needed to invoke and interpret this correctly.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning by explaining that a name is accepted 'as the host says it' with the example 'my quince' — clarifying the fuzzy-name resolution behavior. It does not explain ambiguity handling when a name matches multiple events.

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?

States a specific verb (lists) and resource (an event's team) plus scope (events the signed-in person hosts or co-hosts), and enumerates the returned fields. An agent can immediately distinguish this read tool from the mutation sibling event_team_set.

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?

Clear about the caller context ('the signed-in person hosts or co-hosts') and frames it as the organizer dashboard's Team panel, which implies when to use. It never explicitly names event_team_set as the alternative for changing the team, so the exclusion is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sonar Connections tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?