Grab an exclusive lease on a target (e.g. a PR or branch) for an agent session. Returns null when another agent holds an active lease.
| Name | Required | Description | Default |
|---|---|---|---|
| target_id | Yes | ||
| duration_ms | No | Lease duration (default 5 minutes) | |
| target_type | Yes | e.g. 'pull_request', 'branch' | |
| agent_session_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that acquiring a lease is an exclusive operation and returns null on failure, which adds value beyond annotations. However, it does not detail lease expiration or renewal behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with clear purpose and a key return condition. No unnecessary words, though parameter details are missing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple lease acquisition tool, the description covers core behavior but lacks details on lifecycle (e.g., release requirement) and parameter semantics, making it somewhat incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With only 50% schema description coverage, the description mentions target_type and target_id in examples but fails to explain agent_session_id or duration_ms. The schema already provides some description for duration_ms, but overall adds minimal semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool acquires an exclusive lease on a target (e.g., PR or branch) for an agent session, and specifies the return value when lease is held by another. This distinguishes it from its sibling gluecron_release_lease.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for coordinating exclusive access, but does not explicitly state when to use or when not to use. No alternatives or exclusions are mentioned, leaving the agent to infer context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have near-identical purposes, such as `gluecron_read_file` and `gluecron_repo_read_file` (both read a file from a repo), and `gluecron_explain_repo` and `gluecron_repo_explain_codebase` (both return cached AI explanation). This creates ambiguity despite minor differences in description. While many tools are distinct, the overlapping pairs force an agent to choose between effectively equivalent operations, lowering disambiguation.
All tools use the `gluecron_` prefix followed by a verb_noun pattern (e.g., `acquire_lease`, `create_issue`, `merge_pr`). A few tools like `gluecron_ai_cost_summary` and `gluecron_repo_explain_codebase` deviate slightly but remain readable and predictable. Overall, the naming convention is largely consistent, making it easy to infer tool function from the name.
With 60 tools, the server far exceeds the 25-tool threshold for 'too many' per the guidelines. Although the server covers a broad developer platform (repository management, issues, PRs, workflows, AI features, etc.), the sheer number of tools makes navigation heavy and risks overwhelming both agents and users. A more focused set would improve coherence.
The tool set is remarkably thorough, covering nearly every lifecycle stage for repositories, issues, pull requests, workflows, branches, commits, and AI-assisted features (chat, test generation, release notes, refactoring, voice-to-PR). Essential CRUD operations are present, and advanced operations like leasing, sandbox provisioning, and multi-repo refactoring are included. There are no obvious gaps for the stated purpose of a developer platform.
