Skip to main content
Glama

Organize my roster folders

change_roster_folders
Destructive

Adds, renames, moves or removes a folder, or files rosters in one. Use ids from list_roster_folders and list_my_rosters. For add, supply a new UUID and reuse it if retrying. Use parentId null for the top level or folderId null to unfile rosters. 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": {
      "change": "<change>"
    },
    "name": "change_roster_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeYes
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.4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is covered. The description adds value the annotations cannot: the mcp:manage scope requirement and the idempotency instruction to reuse a new UUID when retrying an add. It does not say what happens to rosters inside a folder that is removed, which matters for a destructive tool.

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?

Four short sentences, front-loaded with the operation set, then id sourcing, retry semantics, null semantics, and permission. Every sentence carries a distinct, actionable fact with no 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 five-variant discriminated-union mutation tool with no output schema, the definition covers what the operations do, where ids come from, idempotency, null handling and authorization. The remaining hole is the blast radius of remove (whether contained rosters are unfiled, deleted, or blocked), which an agent would want before invoking a destructive call.

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?

With 67% schema coverage, the description compensates well by explaining that id values come from the two list tools, that a new UUID must be generated for add, and that null parentId versus null folderId have distinct meanings. It does not clarify rosterIds explicitly or the 40-character name limit, leaving some inference to the schema.

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 opens with a specific verb set and resource: adds, renames, moves, removes a folder, or files rosters in one. It also implicitly differentiates itself from the read-only siblings list_roster_folders and list_my_rosters by naming them as id sources rather than as alternatives.

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 gives concrete usage conditions: pull ids from list_roster_folders and list_my_rosters, pass parentId null for the top level, and folderId null to unfile rosters. It also states the mcp:manage prerequisite. The one gap is no explicit routing away from change_rosters_in_bulk, so overlap with that sibling is left to inference.

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