Skip to main content
Glama

Release lock

lock.release
Destructive

Release a lock with its fencing token. Call keys.create once. Pass caller_key on every later tools/call.

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": {
      "name": "<name>",
      "fencing": "<fencing>"
    },
    "name": "lock.release"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
fencingYes
caller_keyNopf_ key from keys.create. Pass this on tools/call when Authorization and X-Caller-Key are not set. A header key wins if both are set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / caller_key
      Added value: +{
      +  "description": "pf_ key from keys.create. Pass this on tools/call when Authorization and X-Caller-Key are not set. A header key wins if both are set.",
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known, but the description adds nothing about what release destroys, whether the call is idempotent, or what happens when the fencing token is stale or already released. Beyond the boilerplate auth note, the behavior of a destructive mutation is undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, which is good, but the following two sentences are generic auth boilerplate that reads as global guidance rather than tool-specific context. Little space is wasted, yet little of the space spent earns its place for this particular tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, multi-parameter mutation with no output schema and a third of parameters documented, the description should cover lock identity, fencing-token semantics, and failure behavior. Instead it covers only the operation name and a generic credential note.

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 coverage is 33%, so the description must carry weight. It links 'fencing token' to the `fencing` parameter and explains where `caller_key` comes from, adding real value. However, the `name` parameter is never described in either place, and no format or value semantics are given for `fencing`.

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?

States a specific verb and resource: 'Release a lock with its fencing token.' An agent can identify the operation unambiguously. It does not name or distinguish itself from the sibling lock.acquire, which is the natural counterpart, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an auth prerequisite ('Call keys.create once. Pass caller_key on every later tools/call') but no guidance on when to release versus letting a lock expire, whether it must follow lock.acquire, or what to do on a stale fencing token. There is no mention of alternatives or exclusions.

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