Skip to main content
Glama
Sign In
codebugs

codebugs

by faxik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

claims_release

Release a claimed entity to free it for others. Verifies the holder's authorization and returns the outcome, restoring the projected status only if it remains valid.

Instructions

Release a claim. Authorized on the full (holder, holder_kind, holder_repo) triple — pass exactly what you claimed with.

Returns:

  • outcome: released | not_yours | not_claimed | undetermined. A projected status is restored only if it still holds the projected value, so finished work is never resurrected.

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": {
      "entity_id": "<entity_id>",
      "holder": "<holder>"
    },
    "name": "claims_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
holderYes
reasonNoexplicit
entity_idYes
holder_kindNoagent
holder_repoNo
restore_statusNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden. It reveals that releasing is an authorization-gated mutation, enumerates the possible outcomes, and explains the nuanced projected-status restoration rule. This goes well beyond what the schema alone provides.

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?

The description is compact, front-loaded with the core action, and uses a short outcome list. Every sentence adds operational information without filler.

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 6-parameter tool with no annotations, the description covers authorization, outcome semantics, and restoration behavior well. It still leaves entity_id and reason undefined, but the presence of an output schema reduces the need to spell out return details.

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

Parameters3/5

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

The description adds real meaning to the holder/holder_kind/holder_repo parameters by requiring exact match with the original claim, and it hints at restore_status behavior with the projected-value condition. But entity_id and reason are not explained, and schema description coverage is 0%, so parameter guidance remains partial.

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 opens with 'Release a claim,' a specific verb and resource, and clarifies the claim-scoped authorization on the holder triple. It does not explicitly contrast with sibling tools such as release_item, but the resource and operation are unambiguous enough for selection.

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?

It gives clear invocation guidance: pass the exact holder/holder_kind/holder_repo values used when claiming. However, it does not state when to choose this tool over related siblings like claims_who_holds or claims_list, so the when-to-use context is only implied.

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