Skip to main content
Glama

Apply an action to multiple rosters

change_rosters_in_bulk
Destructive

Archives, restores, locks, unlocks, changes visibility or deletes a named set of owned rosters in one operation. Confirm each roster and the exact action, especially deletion or publishing. 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": {
      "ids": "<ids>",
      "action": "<action>"
    },
    "name": "change_rosters_in_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
actionYes
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.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real value on top: the destructive outcome is spelled out (deletion), the visibility-changing actions are enumerated, a confirmation safeguard is prescribed, and the mcp:manage authorization requirement is disclosed. That is meaningful behavioral context beyond the structured fields.

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?

Two short sentences, front-loaded with the operation and scope, followed by the safety caveat and the permission requirement. Every clause carries information an agent needs; there is 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 destructive bulk mutation with no output schema, the definition covers actions, ownership scope, permissions, and confirmation. It omits partial-failure behavior, whether results are reported per roster, and the 100-id batch ceiling, which an agent would want before invoking it at scale.

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 50% schema coverage, the description usefully maps natural-language actions onto the action enum (archive/unarchive, lock/unlock, private/unlisted/public, delete). It says nothing about the ids array — its 1-100 item bounds or the 64-character cap per id — so one required parameter remains undocumented outside the schema.

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 names concrete verbs (archives, restores, locks, unlocks, changes visibility, deletes) and a precise resource ('a named set of owned rosters in one operation'), so the bulk scope and the ownership constraint are both explicit. It doesn't name a sibling such as delete_roster, but the 'in bulk / multiple rosters' framing is enough to separate it from the single-roster operations.

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 clear operational context: confirm each roster and the exact action, with extra caution flagged for deletion and publishing, and states the required permission (mcp:manage). It stops short of naming alternatives or an explicit when-not condition, so the agent must infer that single-roster changes belong to other tools.

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