Skip to main content
Glama
Sign In
codebugs

codebugs

by faxik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

release_item

Mark an item as done or abandoned to free agent capacity, recording the commit SHA when work lands.

Instructions

Free agent capacity for an item.

Args:

  • item_ref: The item id (e.g. CB-5).

  • status: 'done' (terminal) or 'abandoned' (returns item to 'open').

  • commit: SHA where the work landed (recorded if status='done').

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": {
      "item_ref": "<item_ref>"
    },
    "name": "release_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
commitNo
statusNodone
item_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are present, so the description carries full burden. It does disclose key state transitions—'done' is terminal, 'abandoned' returns the item to 'open'—and that commit is only recorded for done. However, it doesn't clarify what 'free agent capacity' concretely changes, side effects on existing claims, or reversibility.

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 short and front-loaded with a clear one-line purpose, followed by a compact, scannable Args list. No filler or redundant restatement of the schema.

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?

The core call contract is covered: all parameters are semantically defined and the state transitions are described. Minor gaps remain around prerequisites (e.g., must the item be currently claimed?) and whether 'done' requires the commit field, but the tool is largely usable as documented.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates: it explains item_ref with an example, enumerates the two status values with their behavioral consequences, and specifies when commit is recorded. This adds substantial meaning beyond the raw JSON schema.

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 ('free') and resource ('agent capacity for an item'), with a concrete item reference example (CB-5). However, it doesn't explicitly distinguish release_item from the sibling claims_release, leaving some ambiguity about the precise workflow.

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?

The Args section gives conditional behavior for status values ('done' terminal, 'abandoned' returns item to open), which implies a workflow. But there's no explicit 'when to use' guidance, no exclusion, and no reference to alternatives like claims_release, so the agent must infer when this tool is appropriate.

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