Skip to main content
Glama
zzhang82

Agent Memory Bridge

claim_signal

Claim pending signals with a short lease to assign ownership to a worker, ensuring fair distribution and preventing duplicate processing.

Instructions

Claim one signal with a short lease for lightweight work coordination.

Use this when a worker should take ownership of a pending signal before it acts. If signal_id is omitted, the bridge claims the next eligible signal in the namespace that matches the optional filters, with a small fairness bias inside the oldest pending window so one polling consumer does not keep winning by accident.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceYesNamespace that holds the coordination events to claim, such as `project:<workspace>`.
consumerYesStable worker or agent identifier that will own the lease, for example `reviewer-a` or `worker:planner`.
lease_secondsNoHow long the claim lease should last before another consumer can reclaim the signal.
signal_idNoOptional exact signal id to claim. Leave empty to claim the next eligible signal.
tags_anyNoOptional OR-style tag filter used to narrow which pending signals are claimable.
correlation_idNoOptional workflow correlation id used to claim signals from one handoff thread.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the fairness bias and optional filters, which adds value. However, it does not mention edge cases like what happens if the signal is already claimed or if the lease expires, leaving some behavioral ambiguity.

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 concise and front-loaded with the core purpose. Two short paragraphs no wasted words. Every sentence adds value.

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?

Given 6 parameters with 100% schema coverage and an output schema exists, the description covers the main use case adequately. It could be slightly more complete by mentioning the outcome format, but the output schema likely covers that.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds minimal extra meaning beyond the schema, only emphasizing that omitting signal_id claims the next eligible signal. This is partially redundant with the schema's default null and description.

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?

The description clearly states the tool claims a signal with a short lease for lightweight work coordination. It distinguishes the action from siblings by focusing on claiming and leasing, but does not explicitly differentiate from similar tools like ack_signal or extend_signal_lease.

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 explicitly states when to use: 'when a worker should take ownership of a pending signal before it acts.' It also explains behavior when signal_id is omitted. However, no exclusions or alternatives are mentioned, such as when to use ack_signal instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zzhang82/Agent-Memory-Bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server