Skip to main content
Glama

Agent inbox

soma_inbox
Read-onlyIdempotent

What waits for the agent: envelopes, signature verification and context packed under a token budget.

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

Input Schema

NameRequiredDescriptionDefault
agentYes
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context that results include envelopes, signature verification, and token-budget packing, but it does not explain how the budget is enforced, whether verification is performed or merely reported, or how the limit affects results.

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?

The description is a single compact sentence with no filler or redundancy. It is somewhat cryptic and front-loads a relative clause rather than a clear action verb, but it is not bloated.

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?

The presence of an output schema and rich annotations reduces the need to document return values and safety characteristics. However, for a tool with two parameters and 0% schema description coverage, the definition leaves core call semantics undocumented, including the meaning of agent and how limit behaves.

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%, yet the description never explains the required agent parameter or the optional limit parameter. The phrase "token budget" vaguely gestures at limit behavior, but it does not clarify whether limit caps item count or interacts with a separate token budget.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It signals that the tool retrieves an inbox of pending items such as envelopes, verification data, and context, but it never uses a clear verb like list, fetch, or read. It also does not distinguish this from siblings such as soma_recall or soma_cold_get, so the purpose is inferable but vague.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling alternative to choose. The phrase "what waits for the agent" weakly implies checking pending work, but call sequencing and alternatives are left unstated.

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