Skip to main content
Glama

unlock

Release a topic lease using the private token issued at lock time so other agents can claim ownership when work completes.

Instructions

Release the lease identified by your token.

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": {
      "topic": "<topic>",
      "token": "<token>"
    },
    "name": "unlock"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe private token returned by lock for this lease.
topicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description must carry the behavioral burden. It does disclose the core effect (the lease is released, i.e. the lock is freed), but says nothing about idempotency, what happens with an expired or unknown token, or whether topic must match the one used at lock time.

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?

A single front-loaded sentence with zero filler; the action and its selector are stated immediately. Nothing is redundant or buried.

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 two-required-parameter mutation tool with no output schema and thin annotations, the description omits the meaning of topic, error and retry behavior, and any lifecycle context. An agent can guess how to call it but not what to expect when the call fails or is repeated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: token is documented in the schema, and the description only restates that the token identifies the lease. The topic parameter has no description anywhere and the description does not explain its role or its relationship to the token, leaving a genuine gap.

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 a specific verb and resource ("Release the lease") and scopes it to the caller's own token. It implicitly complements the lock/renew siblings but never names them, so differentiation is inferred rather than stated.

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?

There is no explicit when-to-use guidance, no mention of when not to call it, and no reference to alternatives such as renew (to extend a lease) or lock_status (to inspect one). The agent must infer the lock/renew/unlock lifecycle from sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools