Skip to main content
Glama

release

Frees a held reservation by ID, or clears all reservations owned by the current agent, allowing other agents to access those resources.

Instructions

Release one of your reservations (id), or all of yours.

Args: id: reservation to release (optional: all of yours).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "release"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.7
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "releaseOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the mutation profile is covered structurally. The description adds real context by disclosing the bulk behavior (omitting id releases every reservation of yours), which is the main risk here, but says nothing about error behavior for an invalid or non-owned id.

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 tight sentences, scope stated first, then the parameter meaning. The Args block slightly duplicates the first sentence but stays short and does not bury the key information.

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?

For a single optional-parameter mutation tool with annotations present and no output schema, the description covers purpose and the bulk-mode semantics. It leaves unclear what a successful release returns (count, confirmation) and what happens on an unknown or foreign id, which matters for an agent sequencing reserve/release calls.

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 0% and the schema only types `id` as an optional string, so the description carries the burden — and it does: it explains that `id` identifies the specific reservation and that omission means releasing all of yours. Missing only format details for the id value.

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?

States a specific verb (release) and resource (your reservations), and clarifies the two modes: single-id or all-of-yours. It does not differentiate itself from close-by siblings such as release_file_reservations or reservations, so the agent must infer which reservation domain this applies to.

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?

Usage is only implied: the description tells you to release a reservation by id or all of yours, which suggests it follows a `reserve`, but it never says when to prefer this over release_file_reservations or how it relates to reserve/reservations. No exclusions or preconditions are stated.

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