Skip to main content
Glama

Lock or unlock a roster

set_roster_locked

Changes the saved roster’s edit lock. This does not change its army or visibility. 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": {
      "id": "<id>",
      "locked": "<locked>"
    },
    "name": "set_roster_locked"
  }
}

Input Schema

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

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

Annotations only declare the generic profile (readOnly=false, destructive=false, openWorld=true). The description adds real value beyond that: the required scope "mcp:manage" and the guarantee that only the edit lock changes while army and visibility are untouched, which tells the agent this mutation has narrow, non-destructive blast radius.

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: the action first, then the scope boundary, then the permission requirement. Nothing is redundant or buried.

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 two-required-parameter toggle with no output schema and adequate annotations, the definition covers action, scope, and authorization. It stops short of stating idempotency or behavior on an invalid roster id, but nothing essential to a correct call is missing.

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?

Schema description coverage is 50% -- llm_model and conversation_id are self-documented, but the two required parameters (id, locked) have no schema descriptions at all. The description partially compensates by establishing that the boolean is an "edit lock" and the id targets a "saved roster," but adds no format or failure semantics. Baseline 3 for mid-level coverage.

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?

"Changes the saved roster's edit lock" names a specific verb and resource, and the second sentence scopes it against adjacent operations (army composition, visibility) that sibling tools like set_roster_visibility handle. An agent can tell what this tool does and does not touch without opening the schema.

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?

The scope exclusion ("does not change its army or visibility") implicitly routes agents to the visibility sibling for that concern, and the permission note signals a prerequisite. There is no explicit when-to-use statement, but the lock/unlock framing makes the trigger obvious.

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