LLM Bus

release

End your active lease on a surface to free it for other agents, preventing collisions in shared workspaces.

Instructions

Release your active lease(s) on a surface.

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": {
      "surface": "<surface>"
    },
    "name": "release"
  }
}

Input Schema

Name	Required	Description	Default
`surface`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

TDQS

C2.4/5.0

Behavior2/5

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

The description only states the action without revealing behavioral traits like what happens if no lease exists, whether it can release another's lease, or if it requires ownership/permissions. With no annotations, the description should carry more burden but fails to do so.

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

Conciseness3/5

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

The description is a single sentence, making it concise and front-loaded. However, it sacrifices necessary detail, so while it earns its place, it does not fully serve the tool's needs.

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?

Given the lack of annotations, no output schema, and a single parameter, the description is inadequate. An agent would have trouble understanding the tool's preconditions, effects, and how it fits with siblings like 'lease' and 'claim'.

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

Parameters1/5

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

The only parameter 'surface' has no schema description and the tool description does not clarify what it means (e.g., surface ID, name). 0% schema coverage means the description should compensate, but it adds no additional meaning.

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 clearly states the action ('release') and the resource ('active lease(s) on a surface'). It distinguishes from the sibling tool 'lease' by implying the opposite operation, but it does not explicitly contrast with other siblings or provide broader context.

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?

No guidance on when to use this tool, prerequisites (e.g., must have an active lease), or when not to use it. The description lacks information about typical scenarios, making it hard for an agent to decide appropriately.

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