Skip to main content
Glama
Sign In

turnale

by app.turnale
OverviewDiscussionsAdmin

End tournament

end_tournament

Finish the tournament. If matches are still pending it ends early and current standings freeze as the final results. Preview first, confirm to apply.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tournament_key": "<tournament_key>"
    },
    "name": "end_tournament"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoOmit or false: return a preview of what would change. True: apply it.
request_idNoOptional idempotency id — retrying a call with the same id never applies it twice
tournament_keyYesThe tournament's organiser key (starts with tk_)

Output Schema

NameRequiredDescriptionDefault
statusYes
previewNoTrue when this is a preview — nothing was changed
summaryYesWhat happened, in one line
placementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses important behaviors beyond the annotations: if matches are pending, the tournament ends early and standings freeze. It also reveals the preview/confirm mechanism. Annotations only state readOnlyHint=false and destructiveHint=false, but the description adds situational context about what happens to pending matches, which is valuable for the agent.

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?

Two sentences, with the main action front-loaded. Every sentence provides necessary context: what happens on early end and the preview/confirm process. No wasted words.

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 tool's moderate complexity, the 100% schema coverage, and the existence of an output schema, the description is complete. It explains the critical behavior (pending matches, freeze) and the confirmation flow, so the agent can select and invoke correctly without further information.

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 input schema has 100% coverage, so the baseline is 3. The description goes beyond by explaining the preview/confirm flow, which directly maps to the 'confirm' parameter. It doesn't detail tournament_key or request_id, but the schema already handles those. The added semantic about preview/confirm elevates it to 4.

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's purpose: 'Finish the tournament.' It specifies the verb and resource, and adds key behavioral detail about early ending and freezing standings, which distinguishes it from sibling tools like delete_tournament or update_settings.

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 clear usage context: preview first, then confirm to apply. It implies when to use (when you want to end the tournament) but does not explicitly mention alternatives or exclusion scenarios. Still, the two-phase preview/confirm guidance is a strong usage guideline.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources