Skip to main content
Glama

Separate a roster variant

split_roster_variant
Destructive

Makes a saved variant a standalone roster without changing its army. 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": {
      "id": "<id>"
    },
    "name": "split_roster_variant"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds two useful facts beyond that: the army contents are preserved, and the call requires the mcp:manage permission. It does not explain what is actually destroyed or altered (presumably the link to the parent roster) or whether the operation is reversible.

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?

Two short sentences, front-loaded with the action and its key invariant, with the permission requirement trailing. No filler. It is arguably too terse for a destructive mutation, but nothing is wasted.

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

Completeness2/5

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

This is a destructive mutation with no output schema, and the description omits what happens to the original variant, whether the parent roster is affected, and what the required id refers to. For a destructive operation the description should carry more of that burden. The permission note is the only compensating detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the one undocumented parameter is the required 'id' — the description never says what it identifies (the variant to split) or what form it takes. The two analytics parameters are covered by the schema, so the description adds nothing there. The description fails to compensate for the gap on the single required input.

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 gives a concrete verb and outcome: 'Makes a saved variant a standalone roster,' which is more specific than the title alone. The clause 'without changing its army' adds a meaningful scope boundary. It stops short of naming a sibling such as copy_roster or save_roster to disambiguate the operation.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no comparison to alternatives like copy_roster or save_roster, which an agent could easily confuse with this operation. 'Requires mcp:manage' is a permission prerequisite, not usage guidance. The agent must infer the scenario from the name alone.

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