Skip to main content
Glama

release

Close the leased browser cleanly and return it to the pool so other agents can use it once you are done.

Instructions

Close the browser cleanly and give it back. Do this as soon as you are done: until then, or until the lease expires, no other agent can use it.

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

Input Schema

NameRequiredDescriptionDefault
browserYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It does disclose valuable context: the close is 'clean', the browser is returned to a shared pool, and other agents stay blocked until release or lease expiry. It omits failure behavior (what if no lease is held or the browser already closed) and whether release is idempotent.

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?

Two short sentences, front-loaded with the action and followed by the urgency/rationale. Nothing is redundant and the key constraint (exclusive lease) lands immediately.

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?

For a single-parameter teardown tool with an output schema, the description covers the important operational facts: what it does, why it matters, and the exclusivity window. The main remaining gap is the meaning/format of the `browser` argument, which the schema leaves entirely undocumented.

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

Parameters2/5

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

There is one required `browser` parameter with zero schema description coverage, and the description never explains it — no guidance on whether it is an ID, name, or object returned from `lease`. At 0% coverage the description should compensate for the parameter, and it does not.

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 gives a concrete verb and resource: close the browser and hand the lease back. It also implies the resource-exclusivity model (a lease exists, other agents wait), which separates it from `lease` (acquire) and `status` (inspect) without naming them. It stops short of an explicit contrast 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 Guidelines4/5

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

Timing guidance is explicit and actionable: 'Do this as soon as you are done', with the consequence of not doing it spelled out. It implies when-not (only when you hold the lease) but does not name an alternative tool or state what to do if you never held one.

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