Skip to main content
Glama

Publish a league draw

publish_league
Destructive

A group organizer publishes the reviewed draw. Use the seed and ordered playerIds from get_my_group. Confirm the fixtures before publishing. Requires mcp:manage.

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": {
      "token": "<token>",
      "seed": "<seed>",
      "playerIds": "<playerIds>"
    },
    "name": "publish_league"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedYes
tokenYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
playerIdsYes
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds the required mcp:manage permission and a confirmation step, but it does not explain what publishing destroys or replaces (e.g., existing fixtures) despite the destructive annotation.

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 four short sentences, front-loads the action, then gives prerequisites and permission requirements. There is no filler, though the sentences could be slightly more integrated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive write tool with 5 parameters, 40% schema coverage, and no output schema, the definition covers provenance and permission but omits what happens to existing league data when publishing and does not explain the required token. It is workable but not complete.

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?

Schema coverage is only 40%, and the description compensates for seed and ordered playerIds by specifying their source in get_my_group. However, the required token parameter is left unexplained, and the llm_model and conversation_id parameters are documented only in schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'publishes the reviewed draw.' The word 'reviewed' differentiates this from generating a draw (draw_league) and signals a later workflow stage, though no sibling is named explicitly.

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?

It gives clear workflow guidance: use the seed and ordered playerIds from get_my_group, and confirm fixtures before publishing. It lacks explicit when-not conditions or named alternatives, but the context is strong enough to route an agent correctly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources