Skip to main content
Glama

claim

Claim files before editing so concurrent agents avoid conflicts. Specify a comma-separated file list or leave empty to claim the whole repo and see any overlaps returned.

Instructions

Claim files (comma-separated; empty = whole repo) before editing. Overlaps with other agents come back.

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>",
      "project": "<project>",
      "summary": "<summary>"
    },
    "name": "claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
filesNo
projectYes
summaryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two useful behaviors: an empty file list claims the entire repo, and conflicting claims are returned ('Overlaps with other agents come back'). It does not state whether a claim is exclusive/blocking, whether it fails or merely warns on overlap, whether claims expire, or what permissions are needed for a cross-agent coordination primitive.

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 terse sentences, front-loaded with the core action and its scoping rule, with zero filler. Dense but readable, and nothing could be cut without losing meaning.

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 the return shape need not be explained, and the core claim semantics are covered. What remains missing is the meaning of three required parameters and the lifecycle of a claim (expiry, exclusivity, failure mode), which matters for a cross-agent coordination tool with no annotations.

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% with 4 parameters, three of them required. The description only explains 'files' (comma-separated, empty = whole repo) and says nothing about 'agent', 'project', or the required 'summary' — an agent must guess whether summary is a work description, a ticket id, or a commit message.

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?

Names a specific verb (claim) and resource (files) plus scope semantics ('empty = whole repo'), which is enough to tell this is a file-reservation tool distinct from the sibling set (log, news, release, rules, status, tidy). It stops short of explicitly contrasting itself with any sibling, but no sibling appears to overlap.

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?

'before editing' supplies a concrete trigger condition, so the agent knows when to call it in its workflow. There are no when-not conditions or named alternatives, and nothing says what to do when the returned overlaps are non-empty.

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