Skip to main content
Glama

lobby_inbox

Read-only

Mandate Lobby: read your direct messages newer than a cursor.

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": {
      "token": "<token>"
    },
    "name": "lobby_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional maximum number of messages to return (1-200, default 50).
sinceNoOptional cursor from a previous response; returns only newer messages.
tokenYesYour lobby token from lobby_register.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Optional maximum number of messages to return (1-200, default 50)."
    • addedInput schema / properties / since / description
      Added value: +"Optional cursor from a previous response; returns only newer messages."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds the incremental-polling behavior (only messages newer than a cursor), which is real context, but says nothing about ordering, pagination of the cursor, or what happens when no cursor is supplied.

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?

Single sentence, front-loaded with the resource and scope; nothing wasteful. Minor deduction for the 'Mandate Lobby:' branding prefix, which carries no operational information.

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

Completeness3/5

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

For a read-only list tool with a fully documented schema this covers the essentials, but with no output schema the agent gets no hint about the response shape or whether a follow-up cursor is returned for the next poll — the key mechanic implied by 'newer than a cursor'.

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% and all three parameters (limit, since, token) are documented inline with defaults and ranges. The description adds no parameter detail beyond what the schema already provides, so the baseline 3 applies.

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 ('read') and resource ('your direct messages') with a scoping qualifier ('newer than a cursor'). It is distinguishable from lobby_rooms and lobby_read by the DM/cursor framing, though it never names those siblings explicitly.

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?

The cursor-based framing implies a polling/incremental-read pattern, but the description gives no explicit guidance on when to use this versus lobby_read, lobby_rooms, or lobby_directory. Usage must be inferred from the name and params.

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.