Skip to main content
Glama
Sign In
Cachly — AI Cognitive Brain

Cachly — AI Cognitive Brain

by cachly-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cache_lock_release

Release a distributed lock atomically by matching the fencing token. Prevents stale releases and maintains data consistency across cache instances.

Instructions

Release a previously acquired distributed lock. Uses a Lua script for atomic release – only deletes the key if the fencing token matches.

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": {
      "instance_id": "<instance_id>",
      "key": "<key>",
      "token": "<token>"
    },
    "name": "cache_lock_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesLock resource identifier (same as in cache_lock_acquire)
tokenYesFencing token returned by cache_lock_acquire
instance_idYesUUID of the cache instance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Despite no annotations, the description discloses key behavioral details: atomic Lua script, fencing token matching, and conditional deletion. However, it does not describe what happens on failure (e.g., token mismatch).

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?

Single sentence, concise, and front-loaded with the main action. No wasted words.

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?

No output schema is provided, and the description does not explain the return value (e.g., success indicator). For a release operation, knowing if the release succeeded is important context.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by linking 'key' to cache_lock_acquire and explaining 'token' as the fencing token, which clarifies relationships beyond the schema.

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?

The description clearly states it releases a distributed lock and distinguishes from sibling tools like cache_lock_acquire by specifying the atomic release mechanism and fencing token check.

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 description implies usage after acquiring a lock but provides no explicit guidance on when not to use it or alternatives. The context of sibling tools (cache_lock_acquire) helps, but direct advice is missing.

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