Skip to main content
Glama

speechwire_list_teams

List all registered teams for the tournament with their IDs, names, codes, and attendance flags. Use to view or manage team rosters.

Instructions

List all teams registered for the tournament.

Returns

list[dict] Team records containing: - team_id: int — numeric team identifier - name: str — team/school name - code: str | None — team code abbreviation - is_invited: bool — whether the team is invited - is_attending: bool — whether the team is attending - is_checked_in: bool — whether the team is checked in - is_udl_member: bool — whether the team is a UDL member

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are present, so the description carries full burden. It details the output schema with six fields and their types, providing good transparency about what the tool returns. However, it does not explicitly state that the operation is read-only or non-destructive.

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 is reasonably concise with a clear heading and structured return fields. It front-loads the purpose and then lists output fields, but the return section is somewhat lengthy. Every sentence is informative.

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?

Given no parameters, an output schema exists (described in detail), and the tool is simple, the description is fully complete. It explains both purpose and return format, leaving no ambiguity about usage.

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?

The tool has no parameters, and the input schema has 100% coverage (empty). With zero parameters, the baseline is 4, and the description adds no parameter information, which is appropriate.

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 teams registered for the tournament' with a specific verb ('list') and resource ('teams'). It differentiates from sibling tools like 'get_team_entries' which focus on individual team entries.

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?

No explicit when-to-use or when-not-to-use guidance is provided. However, the tool has no parameters and a straightforward purpose, so the context is implied. The description does not mention alternatives or exclusions.

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