Skip to main content
Glama

speechwire_add_judge

Add a new judge to a SpeechWire tournament by providing their name and team ID, with optional email, judge type, availability slots, and flags for clean, coach, or priority status.

Instructions

Add a new judge to the tournament.

Parameters

judge_name : str Judge's full name (required). team_id : int Team/school ID (required). Get valid IDs from speechwire_list_teams. judge_email : str Email address (optional). judge_type_id : int Tournament-specific judge type ID from speechwire_list_judge_types. Use 0 when no configured judge type is selected. is_clean : bool Whether the judge is a clean/neutral judge. is_coach : bool Whether the judge is a coach. is_priority : bool Whether the judge is a priority judge. available_slots : list[int] | None Provider slot_id values from speechwire_list_timeslots for which the judge is available. If omitted, the judge is blocked for all slots.

Returns

dict {"success": bool, "judge_id": int | None, "error": str | None}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idYes
is_cleanNo
is_coachNo
judge_nameYes
is_priorityNo
judge_emailNo
judge_type_idNo
available_slotsNo
Behavior4/5

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

With no annotations, the description explains parameter behaviors, such as the default for available_slots ('if omitted, the judge is blocked for all slots') and the return format. It lacks information on auth or side effects, but covers essential behavioral traits.

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?

The description is well-structured with headers and bullet points, each sentence adds value, and it is appropriately sized given the 8 parameters. It is front-loaded with the purpose.

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?

Given 8 parameters, no output schema, and no annotations, the description covers parameter semantics and return value completely. It references sibling tools for validation, making it sufficient for an AI agent to use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description provides extensive explanations for each parameter, including how to obtain valid values (e.g., team_id from speechwire_list_teams) and default behaviors (e.g., available_slots). This adds significant meaning beyond the schema.

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 'Add a new judge to the tournament' with a specific verb and resource. It distinguishes from sibling update tools like speechwire_update_judge_email, making the purpose unambiguous.

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?

The description provides guidance by referencing sibling tools for parameter preparation (e.g., 'Get valid IDs from speechwire_list_teams'). However, it does not explicitly contrast when to use this tool versus other add/update tools or state prerequisites like tournament selection.

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