Skip to main content
Glama
Sign In
Shared Memory MCP Server

Shared Memory MCP Server

by dx-corp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

claim_work_unit

Claim a specific work unit for execution by specifying session, unit, worker, and estimated duration to coordinate task processing in shared memory systems.

Instructions

Claim a specific work unit for execution

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": {
      "session_id": "<session_id>",
      "unit_id": "<unit_id>",
      "worker_id": "<worker_id>",
      "estimated_duration_minutes": "<estimated_duration_minutes>"
    },
    "name": "claim_work_unit"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesSession ID
unit_idYesWork unit ID to claim
worker_idYesWorker claiming the unit
estimated_duration_minutesYesEstimated duration in minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if claiming is exclusive, reversible, requires specific permissions, affects other workers, or has side effects like locking the unit. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence with zero waste. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration, making it easy to parse quickly.

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

Completeness2/5

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

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, return values, error conditions, and how it interacts with sibling tools. This leaves significant gaps for an AI agent to understand the tool's full context.

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 schema fully documents all four parameters. The description adds no additional meaning beyond implying that parameters are used to claim a work unit, which is already inferred from the tool name. This meets the baseline for high schema coverage.

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 action ('claim') and resource ('work unit for execution'), making the purpose understandable. It doesn't distinguish from sibling tools like 'publish_work_units' or 'update_work_status', which prevents a perfect score, but the verb+resource combination is specific enough for basic understanding.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'publish_work_units' or 'update_work_status'. It lacks context about prerequisites, such as whether a work unit must be unclaimed or available, and offers no explicit when-not or alternative scenarios.

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