Skip to main content
Glama

Delete my roster

delete_roster
DestructiveIdempotent

Permanently deletes one of the signed-in player's saved rosters, by an id from list_my_rosters, and ends any loan of it to a friend. Battles it was fielded in keep their own record. It cannot be undone, so confirm the roster's name with the player first; set_roster_archived hides a list without losing it. 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": "delete_roster"
  }
}

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. 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 already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, yet the description still adds non-obvious consequences: any loan of the roster to a friend is ended, and battles it was fielded in retain their own record. It also discloses the mcp:write scope requirement. The only gap is that it never says what the call returns on success or failure.

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 tight sentences with the irreversible-deletion warning and the pre-call confirmation step front-loaded ahead of the alternative and the permission note. Every clause carries information; nothing is filler.

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 destructive, non-idempotent-looking operation with no output schema, the definition covers provenance of the id, side effects on other entities, irreversibility, prerequisite confirmation, the non-destructive alternative, and the required permission. The only missing element is what the agent receives back after the delete.

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 description coverage is 67%, and the one uncovered property is the required id, whose meaning the description supplies (a roster id obtained from list_my_rosters). The two analytics parameters are self-documented in the schema and need no further explanation, so the description fills exactly the gap the schema leaves.

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?

States a specific verb and resource (permanently deletes a saved roster) plus the scope constraint that it must be the signed-in player's own roster, and names the source of the identifier (list_my_rosters). It also implicitly contrasts with set_roster_archived, which is named later, so an agent can distinguish it from siblings without opening a 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?

Explicitly tells the agent where the id comes from, that deletion is permanent, that the player's confirmation of the roster name should be obtained first, and that set_roster_archived is the correct alternative when the goal is merely to hide. That is the when/when-not/alternative triad in full.

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