Skip to main content
Glama

speechwire_list_judges

Retrieve a complete list of judges registered for a SpeechWire tournament, including roster details such as name, team, and availability.

Instructions

List all judges registered for the tournament with roster details.

Returns

list[dict] Judge records containing: - judge_id: int — numeric judge identifier - name: str — judge's full name - team: str | None — school or team name - team_id: int | None — numeric team identifier - is_coach: bool — whether the judge is marked as a coach - is_active: bool — whether the judge is active - is_clean: bool — whether the judge is marked clean - is_priority: bool — whether the judge is marked priority - email: str | None — judge's email address (if present on the roster page) - unavailability: str | None — unavailability summary text - blocks: list[str] — event/team blocks (e.g. "GROUPING: Varsity Policy Debate")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations are absent, so the description must communicate behavioral traits like read-only nature. The description only details the return format but does not explicitly state that the tool is safe, read-only, or has no side effects. This leaves uncertainty for the agent about whether invoking the tool could alter state.

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?

The description starts with a clear one-sentence summary. The subsequent bullet list of return fields is structured and adds useful information, but given the presence of an output schema, it could be considered slightly redundant. However, it is not overly verbose and is well-organized.

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?

The description covers the core purpose and provides comprehensive detail on the return format. It does not mention error conditions or preconditions like requiring a tournament context, but the output schema fills in return details. Given the tool's simplicity (no parameters) and the presence of output schema, the description is adequately complete.

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?

There are no parameters in the input schema, so parameter semantics are not applicable. Baseline score of 4 is appropriate as the tool requires no arguments. The description correctly provides no parameter-specific guidance since none exist.

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 clearly states 'List all judges registered for the tournament with roster details' specifying the verb (list) and resource (judges). The tool name itself also clearly indicates the purpose, and it is distinct from sibling tools which address other resources like rooms, teams, or user accounts.

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?

The description provides no guidance on when to use this tool versus the many judge-related siblings such as speechwire_get_judge_school or speechwire_add_judge. It does not mention prerequisites like having a tournament selected or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jessica-writes-code/speechwire-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server