Skip to main content
Glama

Archive or restore my roster

set_roster_archived
Idempotent

Archives one of the signed-in player's saved rosters, which moves it out of their main roster list without deleting it, or restores it with archived false. 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>",
      "archived": "<archived>"
    },
    "name": "set_roster_archived"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
archivedYes
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.2/5.0
Behavior4/5

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

Beyond the annotations, the description adds important behavioral context: archiving removes the roster from the main list without destroying it, restoring is done with archived false, and the operation requires the mcp:write scope. The annotations already declare idempotency and non-destructiveness, and the description reinforces the reversible, non-deleting nature of the operation.

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?

The description is a single efficient sentence that front-loads the primary action, explains the non-deleting archive behavior, gives the restore condition, and states the required scope. There is no redundant or filler wording.

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?

For a simple mutation tool with annotations covering safety and idempotency and no output schema, the description supplies the key context an agent needs: what changes, what does not change, how to restore, and the auth requirement. It does not describe error cases or return behavior, but those are less critical here given the annotations and simple parameters.

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?

The description explains the meaning of the archived boolean by saying restore uses archived false, and it implies that id identifies one of the signed-in player's saved rosters. The other two parameters are documented only in the schema, and with 50% schema description coverage the description partially but not fully compensates for the remaining parameter semantics.

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 states a specific verb and resource: archiving or restoring one of the signed-in player's saved rosters. It immediately distinguishes the operation from deletion by explaining that the roster is moved out of the main list without being deleted.

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 clearly establishes when to use the tool for archiving versus restoring, with archived false controlling the restore direction. It also implicitly distinguishes this from delete_roster by noting the roster is not deleted, but it does not explicitly compare with set_roster_visibility or other roster-management alternatives.

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