Skip to main content
Glama

Create a battle join link

share_battle_invite

Creates or returns the join link for a battle the player can share. Anyone who has the link can use it to take an open place. 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": "share_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

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds real context beyond them: that the call may return an existing link rather than always minting a new one, that possession of the link grants a seat, and that mcp:manage scope is required. It stops short of covering link lifetime, revocation, or whether repeat calls are idempotent.

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 sentences, front-loaded with what the tool does, followed by the effect and the permission requirement. No filler or redundancy.

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

Completeness4/5

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

With only three parameters, no nested objects, and no output schema, the definition covers the essentials: what is produced (a join link), who can use it, and the authorization scope. The remaining gaps, mainly the undocumented required token and the absent link-expiry semantics, are modest for a tool of this complexity.

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%. The two documented parameters (llm_model, conversation_id) are analytics fields, while the sole required parameter, token, has no schema description and is not explained in the description either, so the agent gets no help identifying what the token represents. The description adds no parameter-level meaning at all.

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 names a specific verb-plus-resource: it creates or returns a shareable battle join link. It also states the audience and effect ('Anyone who has the link can use it to take an open place'), which distinguishes it from a read-only lookup such as get_battle_invite or a direct invite such as invite_friend_to_battle.

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 implied by the sharing scenario and the mcp:manage requirement, which lets an agent infer when the tool is applicable. However, it never says when to prefer this tool over get_battle_invite, invite_friend_to_battle, or stop_sharing_battle_invite, and gives no explicit exclusions.

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