Skip to main content
Glama

release

Clears an agent’s claims in the aisync Multi-Agent Context Management hub, removing all claims or only those for a specified project so other agents can proceed.

Instructions

Release your claims (all of them, or one project's).

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

Input Schema

NameRequiredDescriptionDefault
agentYes
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden for what is evidently a state-clearing mutation. It never says whether released claims are recoverable, whether others can release another agent's claims, whether calling it with nothing held is an error or a no-op, or whether the operation 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.

Conciseness4/5

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

One short sentence, front-loaded with the verb and resource, with the scope variant in a parenthetical. No filler, but the brevity borders on under-specification given the missing behavioural detail.

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?

An output schema exists, so return format need not be described. However, for a two-parameter mutation with zero annotation coverage and zero schema descriptions, the definition leaves too much of the calling contract unexplained, particularly the required agent identity and the semantics of the empty default for project.

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?

Schema description coverage is 0%, so nothing documents the two parameters externally. The description only gestures at the scope behaviour of "project" (via "one project's") and says nothing about the required "agent" parameter, including whether it identifies the caller or the target holder — a meaningful ambiguity for a release operation.

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 and resource ("Release your claims") plus the scope of the operation ("all of them, or one project's"), which is more than a restatement of the name. It reads as the natural inverse of the sibling "claim", though it never names that sibling, so the pairing must be inferred.

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?

Implicit guidance only: the tool is for freeing claims, and the parenthetical tells you to choose between the all-claims and per-project scope. There is no statement of when a caller should release versus keep a claim, no precondition (must you hold the claim first?), and no reference to alternatives among the siblings.

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