Skip to main content
Glama

Claim an envelope

soma_claim

Take an envelope from the queue exclusively and get context packed under its budget. If the work carries a price, a receipt is required.

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": {
      "id": "<id>",
      "agent": "<agent>"
    },
    "name": "soma_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
agentYes
paymentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / payment
      Added value: +{
      +  "default": "",
      +  "title": "Payment",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false, idempotentHint=false and non-destructive mutation, so the agent knows this changes state. The description adds two genuinely new traits: the claim is exclusive (a lock-like behavior not present in annotations) and payment may be required. It omits the failure modes that matter most for a non-idempotent claim — conflict handling, claim expiry, and whether a release step exists.

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 short sentences with no filler, and the core action and its exclusivity are front-loaded before the conditional payment caveat. Each sentence carries distinct information.

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?

An output schema exists, so return shape need not be explained. But for a non-idempotent, state-mutating claim with three undocumented parameters, the description leaves out parameter meaning, conflict/expiry behavior, and the release path. It is thin relative to the tool's complexity.

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%, so the description carries the full burden for three parameters and largely fails. 'Payment'/'receipt' loosely maps to the payment field, but 'id' (presumably the envelope identifier) and 'agent' (presumably the claiming identity) are never explained, nor is the empty-string default for payment. Critical meaning is left to guesswork.

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?

States a specific verb and resource: 'Take an envelope from the queue exclusively' plus returning 'context packed under its budget.' That distinguishes it from retrieval siblings such as soma_cold_get or soma_inbox by implying a state-changing, exclusive dequeue. It stops short of naming any sibling to contrast with, so the differentiation is inferred rather than explicit.

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

Usage Guidelines3/5

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

Usage is implied — you claim when you are ready to work an item off the queue — and the sentence 'If the work carries a price, a receipt is required' adds a real precondition. However, there is no explicit when-not guidance, no mention of soma_complete for releasing a claim, and no statement of what happens if the envelope is already claimed. An agent must infer the workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources