Skip to main content
Glama
Sign In

Cactal

by ai.cactal
OverviewDiscussionsAdmin

Acquire the edit lease

websiteSourceCode_lease_acquire

Acquires and replaces the website's single edit lease, taking over from any other editor. Writes that pass the returned principal-bound leaseToken keep working until someone else takes the lease; writes without a token take the lease automatically unless another editor is still working: the Cactal agent while it runs, or another caller that wrote in the last 5 minutes.

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": {
      "websiteId": "<websiteId>"
    },
    "name": "websiteSourceCode_lease_acquire"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the lease is single and gets replaced, the token is principal-bound, other holders keep working until preempted, and there is a 5-minute activity window plus an agent-occupancy rule. Annotations (non-read-only, non-idempotent, non-destructive) are consistent with a takeover operation. Missing: whether acquisition can fail, and how/when a lease expires or is released.

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?

Front-loads the core action in the first clause and packs the token semantics into the remainder with no filler. The second sentence is dense and long, but every clause carries operational meaning.

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?

No output schema exists, and the description does name the returned leaseToken and its principal binding, which is the key return value an agent needs. It leaves open failure behavior and lease lifetime, which are relevant for a non-idempotent takeover operation.

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% and the only parameter, websiteId, is never mentioned or qualified in the description. Its name and type make it largely self-evident, so the omission is tolerable but the description does not compensate for the coverage gap by explaining scoping or preconditions.

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?

States a specific verb and resource: acquire and replace the website's single edit lease, explicitly taking over from any other editor. No sibling tool deals with leases, and the description makes the exclusive-ownership model unambiguous.

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?

Explains both paths clearly: call this to hold a token, or write without a token to have the lease taken implicitly. It gives the exclusion condition (another editor active within 5 minutes, or the Cactal agent running) but stops short of saying when an agent should prefer acquiring explicitly versus relying on implicit acquisition.

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

All Cactal toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources