Skip to main content
Glama
naw103

Foremerge

by naw103
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Claim semantic work

claim_work

Claim specific scopes of an intent for a limited lease, notifying other agents you are working on them before starting. This prevents duplicate work and records overlapping claims as warnings.

Instructions

Tell other agents you are working on specific scopes of your own intent, for a limited time. Use this after publish_intent and record_assessment, and before start_work. Claims are advisory and never lock: if any other intent, another of yours included, holds a live claim on a matching scope (symbols match loosely by name), you still get the claim, and a claim-overlap conflict is recorded and returned as a warning. The first claim moves the intent from INTENT to CLAIMED. Claiming a scope the intent already holds renews its lease instead of adding a second claim, which is how long-running work keeps its claims. Only the intent's owner may claim, and only while the intent is INTENT, CLAIMED or IN_PROGRESS. Returns the created or renewed claims, overlap warnings, and advisory_only: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoOptional note shown to other agents explaining why you hold the claim.
scopesYesThe scopes to claim. Use the scopes declared on the intent; operations are not repeated here.
agent_idYesYour agent id (agt_...). Must own the intent.
intent_idYesYour intent (int_...) that the claims belong to.
lease_secondsNoHow long the claim lasts before it expires, from 60 seconds to 24 hours. Default one hour. Claim again to renew.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.4.3
    • addedInput schema / properties / agent_id / description
      Added value: +"Your agent id (agt_...). Must own the intent."
    • addedInput schema / properties / intent_id / description
      Added value: +"Your intent (int_...) that the claims belong to."
    • addedInput schema / properties / lease_seconds / description
      Added value: +"How long the claim lasts before it expires, from 60 seconds to 24 hours. Default one hour. Claim again to renew."
    • addedInput schema / properties / reason / description
      Added value: +"Optional note shown to other agents explaining why you hold the claim."
    • addedInput schema / properties / scopes / description
      Added value: +"The scopes to claim. Use the scopes declared on the intent; operations are not repeated here."
    • addedInput schema / properties / scopes / items / properties / key / description
      Added value: +"The name within that kind, for example PaymentService, POST /orders, or src/billing.rs. Comparison is case-insensitive."
    • addedInput schema / properties / scopes / items / properties / kind / description
      Added value: +"What sort of thing the scope names: a code symbol, an API route, a data schema, a config key, infrastructure, a test, a migration, an environment variable, a file path, a component, a contract, or a broader domain."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes far beyond annotations: discloses that claims never lock, that overlap still grants the claim and records a warning, that re-claiming renews the lease instead of adding a second claim, that the first claim moves the intent to CLAIMED, and that the result includes advisory_only: true. This fully describes side effects and semantics.

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 dense but every sentence contributes: purpose, workflow position, locking semantics, renewal behavior, ownership/state constraints, and return payload. It front-loads the core purpose before diving into edge-case behavior.

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?

For a stateful, advisory claim operation with no output schema and no idempotency hint, the description covers success behavior, failure/conflict handling, state transitions, expiry/renewal, and return contents. An agent has enough information to call it correctly and understand consequences.

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

Parameters4/5

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

The input schema already documents all five parameters with 100% coverage, so the baseline is 3. The description adds value by clarifying that scopes must be those declared on the intent, by explaining the loose-by-name overlap matching, and by describing renewal behavior tied to lease_seconds. It does not add per-parameter syntax, but the schema already covers that.

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?

The description states a specific verb and resource: claim semantic work on scopes of your own intent for a limited time. It also places the operation in a workflow (after publish_intent and record_assessment, before start_work) and contrasts it with start_work by saying claims are advisory and non-locking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives the when-to-use context: 'Use this after publish_intent and record_assessment, and before start_work.' It also states constraints (only the intent's owner, only while intent is INTENT/CLAIMED/IN_PROGRESS) and tells the caller to use the intent's declared scopes, which routes the agent away from inventing scopes.

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