Skip to main content
Glama

lock

Reserve a topic and return a token for renewing or releasing ownership so agents avoid conflicting work.

Instructions

Reserve a topic and return the token required for renewal and release.

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>"
    },
    "name": "lock"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNo
noteNo
topicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

annotations declare readOnlyHint=false and openWorldHint=false, so the agent already knows this mutates state, and the description usefully adds that a token is issued as a side effect. It omits the behaviors an agent most needs: that the reservation expires (ttl), what happens on contention for an already-locked topic, and whether stale locks block others.

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

Conciseness4/5

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

A single front-loaded sentence with no filler and no repetition. It is arguably over-compressed for a stateful lifecycle tool, but nothing in it is wasted.

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

Completeness3/5

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

Enough to attempt a call on a topic, but thin for a stateful mutation with three undocumented parameters and no output schema: the token's lifetime, contention behavior, and release obligation are left implicit.

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 0% across three parameters, so the description must compensate and only partially does: it names the topic and hints at the token. The ttl parameter, which governs how long the reservation holds, and note are given no meaning beyond their names and constraints.

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?

"Reserve a topic" gives a specific verb and resource, and the return value is named ("the token required for renewal and release"). It reads clearly as the acquisition half of a lock lifecycle alongside renew/unlock/lock_status, though it never explicitly contrasts with those siblings.

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

Usage Guidelines3/5

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

The mention that the returned token is needed for renewal and release implies the follow-on workflow, which is useful context. But there is no explicit when-to-use guidance, no statement about what happens if the topic is already locked, and no pointer to unlock/renew as the required counterparts.

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