Skip to main content
Glama

Copy a roster

copy_roster

Saves a copy of a roster to the signed-in player's account: one of their own from list_my_rosters, or a public or unlisted one they can open. variant true keeps the copy grouped with the original as an alternative version, which only works on their own rosters; false makes a standalone copy. The copy takes the player's default visibility, which is public unless they changed it, whatever the original's. Returns the new roster's id, url and visibility: tell the player when it is public, and offer set_roster_visibility. Requires mcp:write.

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": "copy_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
variantNoGroup the copy with the original as a variant; only for the player’s own rosters.
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. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare the write/non-idempotent profile; the description adds the non-obvious side effect that the copy inherits the player's default visibility rather than the original's, which is exactly the kind of behavioral detail annotations cannot carry. It also discloses the mcp:write auth requirement and the returned id/url/visibility, though it does not cover rate limits or failure modes such as copying a roster the player cannot open.

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?

Four sentences, front-loaded with the core action, and no filler; each sentence carries a distinct rule (source, variant, visibility inheritance, follow-up/permission). Slight deduction for the densely nested visibility clause that takes a second read.

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 mutating tool with no output schema, the description covers the return shape (id, url, visibility), the auth scope, the visibility inheritance rule, the variant restriction, and the recommended next action. An agent has everything needed to call it and to explain the result to the player.

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?

Schema coverage is 75%, so the schema already documents variant, llm_model, and conversation_id. The description still adds value by explaining the id's accepted provenance and by spelling out the consequence of variant (grouped alternative vs standalone) beyond the terse schema description.

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?

"Saves a copy of a roster to the signed-in player's account" names a specific verb, resource, and scope, and immediately anchors the source roster to list_my_rosters or a public/unlisted roster the player can open. The agent can distinguish this from save_roster, import_roster, and export_roster without opening any schema.

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

Usage Guidelines5/5

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

It states when variant=true is legal (only the player's own rosters) and when false applies (standalone copy), plus where valid ids come from. It also routes the agent to a follow-up action, set_roster_visibility, conditioned on the copy being public.

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