Skip to main content
Glama
Sign In
codebugs

codebugs

by faxik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

claims_claim

Claim a finding or requirement for exclusive work, preventing parallel-agent collisions and optionally moving it to in_progress.

Instructions

Claim a finding or requirement so parallel agents do not collide.

Args:

  • entity_id: CB-N, FR-N or NFR-N

  • holder: who is claiming — a branch name, agent id, or person

  • holder_kind: branch | agent | human

  • holder_repo: absolute path of the repo owning the branch, if any

  • note: free-text reason, kept on renewal unless replaced

  • project: also move a finding to in_progress (requirements never project)

  • allow_terminal: claim even if the entity is already resolved

Returns:

  • outcome: claimed | already_mine | held_by_other | entity_terminal | undetermined. On held_by_other the holder fields name the INCUMBENT. On undetermined, re-issue the identical call — it converges on already_mine.

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_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
holderYes
projectNo
entity_idYes
holder_kindNoagent
holder_repoNo
allow_terminalNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job: it discloses outcome values, the side effect for project, the allow_terminal override, and the convergence behavior on undetermined. It does not discuss persistence or permissions, but for a claim tool the core behaviors are covered.

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 front-loaded with a one-line purpose, then organized Args/Returns sections. Every line carries genuinely useful information; nothing is redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity, seven parameters, and no annotations, the description fully equips an agent to call the tool correctly: it explains entity ID formats, holder semantics, option effects, and all possible outcomes including the recovery path. The output behavior is documented despite the output schema.

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?

Schema description coverage is 0%, so the description must compensate, and it does: every one of the seven parameters is explained with types/domains and edge-case behavior (e.g., note renewal, project exception). This adds substantial meaning beyond the bare schema titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Claim') and resource ('a finding or requirement'), and gives the coordination rationale ('so parallel agents do not collide'). This distinguishes it from query-style claim siblings like claims_who_holds and claims_list.

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?

The description provides clear context: use it to claim a finding or requirement and avoid parallel-agent collisions. It does not explicitly name alternatives or when-not-to-use conditions, but the purpose is unambiguous and sufficient for selection.

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