Skip to main content
Glama

turnale

by app.turnale

Get PDF document

get_pdf
Read-only

The printable PDF itself, returned as a base64 embedded resource — use this when the organiser wants the file handed to them and your client cannot fetch URLs. Default "sheet": the merged tournament document (match sheet with write-in score boxes, player sheet, standings/results when they exist). "results" and "plan" are deprecated pre-merge variants kept for comparison. For a lighter response, get_pdf_link returns download URLs instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docNo
tournament_keyYesThe tournament's organiser key (starts with tk_)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdf_urlYes
filenameYes
mime_typeYes
size_bytesYes

TDQS

A4.9/5.0
Behavior5/5

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

The description adds valuable behavioral context beyond the readOnlyHint annotation: it returns base64 embedded data, explains the default 'sheet' document (merged tournament document), and notes that 'results' and 'plan' are deprecated pre-merge variants. This is richer than typical annotation-only transparency.

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 concise and front-loaded with the core purpose, followed by usage guidance and parameter details. Every sentence contributes essential information without redundancy, making it highly efficient.

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 the presence of an output schema and annotations, the description fully covers the necessary context: when to use, what it returns, the default document, deprecated options, and an alternative. No gaps remain for a decision-making agent.

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 description provides semantic meaning for the 'doc' parameter that the schema lacks, including the default value and deprecated variants. The tournament_key is already described in the schema, so the description complements rather than repeats. Since schema coverage is 50%, the description adds significant value for the undocumented parameter.

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?

Clearly states the tool returns the printable PDF as a base64 embedded resource, which is a specific verb+resource pairing. The description distinguishes it from get_pdf_link and explains the default document type, making its purpose unmistakable.

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?

Explicitly provides when-to-use guidance: 'use this when the organiser wants the file handed to them and your client cannot fetch URLs.' It also names the alternative get_pdf_link for lighter responses, giving clear criteria for selection.

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

All turnale toolsInspect
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.

Resources