turnale

Get tournament briefing

get_briefing

Read-only

Compact full state of the tournament — settings, roster, progress, next matches, standings, page link. Call this first when resuming work in a new conversation with just the key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tournament_key`	Yes	The tournament's organiser key (starts with tk_)

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`aside`	Yes	Present ONLY when the tournament is set up, running, and asking nothing of the organiser — for answering 'what else can you do?', or any moment where they are plainly just chatting. NEVER volunteer it: not as a greeting, not after a result, not alongside a report. Say `lead` then `text`, nothing of your own in between. Both are English already: relay them unchanged unless the organiser is writing to you in another language. If they are, translate `lead` — but translate `text` ONLY when kind is 'fact'. A joke goes out in English word for word, whatever language you are speaking, because translating it destroys it.
`sport`	Yes
`courts`	Yes
`format`	Yes
`signup`	Yes
`status`	Yes
`next_up`	Yes
`players`	Yes
`page_url`	Yes
`discipline`	Yes
`start_time`	Yes
`players_total`	Yes
`standings_top`	Yes
`matches_played`	Yes
`matches_pending`	Yes
`page_results_entry`	Yes	True when anyone with the page link can record scores courtside (the default for new tournaments). Turn it off with update_settings page_results_entry: false.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat safety guarantees. The description adds value by explaining the tool returns a compact aggregated snapshot, which is consistent with the read-only annotation. It doesn't contradict any annotations and provides useful context about the scope of data included.

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 two sentences long, with the first sentence front-loading the tool's purpose and components, and the second providing usage guidance. Every word contributes meaning, with no filler or redundancy. It is appropriately sized for the tool's complexity.

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?

The description is complete given the existing schema and output schema. It specifies exactly what data the briefing includes, making it clear what the agent can expect. Combined with annotations and sibling context, the agent can confidently select and invoke this tool without further information.

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

Parameters3/5

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

The schema fully documents the single parameter (tournament_key) with a clear description and example format. The description adds no additional parameter-level detail beyond noting it's 'just the key', which is already covered by the schema. With 100% schema coverage, a baseline score of 3 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 the tool provides a 'compact full state' of the tournament, listing specific components (settings, roster, progress, next matches, standings, page link). This distinguishes it from sibling tools like get_standings or list_matches, which focus on individual aspects. The verb 'get' and resource 'briefing' are unambiguous.

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

Usage Guidelines5/5

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

The description explicitly instructs to 'Call this first when resuming work in a new conversation with just the key.' This gives a clear when-to-use directive and prioritizes it over alternatives. It implies the tool is the initial context-gathering step, making the usage scenario very clear.

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

All turnale tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

Several tools serve overlapping purposes: get_pdf and get_pdf_link both return PDF artifacts, get_schedule and list_matches both provide match scheduling info, and get_results vs. get_standings can be confused for finished tournaments. However, the descriptions clarify the distinctions (embedded vs. link, upcoming vs. all matches, final vs. current standings), and roster-management tools are clearly separated by action.

Naming Consistency5/5

All 30 tools consistently use lowercase snake_case with a verb_noun pattern (e.g., create_tournament, record_results, withdraw_player). The only slight variation is the mix of get_* and list_* for read operations, but that's a common and predictable convention. There are no camelCase or inconsistent verb styles.

Tool Count2/5

With 30 tools, the server exceeds the 'too many' threshold of 25. While the domain is complex, this count is heavy and may overwhelm agents, especially since several tools could be consolidated (e.g., get_pdf/get_pdf_link, get_schedule/list_matches). A more streamlined set around 20 tools would be more appropriate.

Completeness5/5

The tool set provides comprehensive lifecycle coverage for tournament management: create/delete/end tournaments, manage players (add, remove, replace, withdraw, promote, update), generate draws, record results, handle doubles pairs, reschedule, retrieve standings/schedule/results, export/PDF, audit log, undo changes, and feedback. No major gaps are apparent for the stated purpose.

Get tournament briefing

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources