Skip to main content
Glama

Retire a battle join link

stop_sharing_battle_invite
Destructive

Disables a battle’s existing join link. People already seated keep their places. 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>"
    },
    "name": "stop_sharing_battle_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
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.9/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-read-only, open-world operation, so the bar is lower, and the description still adds real behavioral context: it discloses that the link stops working while 'people already seated keep their places,' which defines the blast radius of the destructive action. It also adds the 'mcp:manage' scope requirement, which annotations do not express, though it says nothing about whether the link can be restored or what happens to in-flight invitees.

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?

Three short, front-loaded sentences that each carry distinct information: the action, its effect on existing participants, and the required permission scope. No filler or restatement of the title.

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?

For a small three-parameter mutation with no output schema, the description covers the action, its destructive extent, and the authorization requirement, which covers what an agent needs before invoking it. Remaining gaps, such as return value and irreversibility, are minor against a tool this simple.

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 67%, so the header parameters (llm_model, conversation_id) are documented in the schema. The single required parameter, token, has no schema description and the description never explains that it is the invite token identifying which link is retired, leaving the most important parameter opaque. Baseline 3 is appropriate given partial coverage and no added meaning.

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: it 'disables' a battle's 'existing join link,' which separates it from the share/get invite siblings without naming them. It is clear about scope (the link, not the battle or the players), though it never explicitly contrasts itself with the sibling tools that create or inspect invites.

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

Usage Guidelines3/5

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

Usage is only implied: the reader infers this is the tool for revoking an invite after distribution, and the 'Requires mcp:manage' note gives a permission prerequisite. There is no explicit when-to-use vs when-not statement and no named alternative (e.g. re-sharing via share_battle_invite or inspecting via get_battle_invite).

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