Skip to main content
Glama
naw103

Foremerge

by naw103
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Claim semantic work

claim_work

Claim a time-limited advisory scope for your intent so other agents see what you are working on and overlap conflicts are warned before code changes begin.

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, advisory_only: true, and scope_warnings when a symbol key will lose its class.

Input 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.8/5.0
Behavior5/5

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

Annotations only declare the read/write safety profile; the description supplies the substantive semantics — claims are advisory and never lock, overlapping claims still succeed but produce a recorded warning, the first claim transitions INTENT→CLAIMED, and re-claiming renews the lease rather than duplicating. It even discloses the return payload components, which is critical given there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence and every subsequent sentence carries non-obvious information (ordering, advisory nature, renewal, ownership, returns). It is dense — the third sentence bundles advisory semantics, conflict handling, and warnings — but no sentence is filler.

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 mutating, non-idempotent tool with no output schema, the description covers the state machine, authorization constraint, the renewal idiom, the conflict-warning behavior, and the shape of the response. Nothing an agent needs in order to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning on top by explaining that symbol matching is loose and case-insensitive by name, and that re-claiming an existing scope renews the lease (the practical use of lease_seconds for long-running work). It does not restate the enum or the 60s–24h bounds, but the schema already covers those.

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?

Opens with a concrete verb+resource: registering an advisory claim on scopes of your own intent for a limited time. It distinguishes itself from siblings by naming publish_intent, record_assessment, and start_work as the surrounding sequence, so an agent knows exactly where this sits in the workflow.

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 states when to use it ('after publish_intent and record_assessment, and before start_work') and what alternative behavior to expect ('Claiming a scope the intent already holds renews its lease instead of adding a second claim'). It also states the preconditions: owner-only, and only while the intent is INTENT, CLAIMED, or IN_PROGRESS.

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