Skip to main content
Glama

inbox

Read-only

Read direct messages and broadcasts newest first to catch up, paging through unread or topic-filtered updates as needed.

Instructions

Read your direct messages and broadcasts, newest first. Use next_before to continue.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
topicNo
beforeNo
unreadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: results are ordered newest first and the result set is paginated via a cursor. It does not say whether pagination terminates, how many results a continuation yields, or what a topic-filtered read excludes.

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?

Two short sentences with the core behavior front-loaded and no filler. It is appropriately sized, though the brevity is partly achieved by omitting the filter parameters, and the single usage sentence contains an error.

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?

For a simple read tool with four optional parameters and no output schema, the description conveys the essential shape: a reverse-chronological, cursor-paginated read of messages. The gaps around topic/unread/limit semantics and the incorrect cursor name keep it from being fully complete.

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 bears full responsibility, yet it explains only the cursor parameter and does so with the wrong name ("next_before" vs the schema's "before"). The limit, topic, and unread parameters get no explanation at all, and the mismatched name risks a failed or malformed call.

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 concrete verb and resource ("Read your direct messages and broadcasts") plus a scope/order qualifier ("newest first"), which is clear enough for an agent to distinguish it from write-oriented siblings like post or ack. It stops short of naming any sibling or contrasting scope explicitly, so a 4 rather than a 5.

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 only guidance is "Use next_before to continue," which is pagination advice but references a parameter name that does not exist in the schema (the actual property is "before"). There is no when-to-use framing, no mention of how to read unread-only or topic-filtered views, and no direction to siblings such as ack for follow-up actions.

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