Skip to main content
Glama

inbox

Fetch unread messages from worldinmotion and mark them read unless peek is enabled, letting agents review content without changing read status.

Instructions

Unread items; marks them read unless peek.

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
peekNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the critical non-obvious behavior: the call mutates state by marking items read. That is the single most important disclosure. It omits whether the marking is per-user or global, whether it is reversible, whether it requires auth, and what the response contains.

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?

Seven words, front-loaded with the primary effect and immediately qualified by the flag that changes behavior. Nothing is padded, though the telegraphic style borders on under-specification rather than tightness.

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 single-parameter read tool with no output schema and no annotations, the description covers the essential side effect but leaves the nature of the returned items, ordering, and pagination unaddressed. Adequate to call correctly, thin on what to expect back.

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 0%, so the schema supplies only the name and type of peek. The phrase "unless peek" adds real meaning by tying the flag to suppression of the read-marking side effect, which the schema cannot convey. It still leaves the default value (presumably false) and the exact semantics of a peek=true call unstated.

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?

"Unread items" names the resource and its filter state, but there is no verb and no statement of what the items are (messages, notifications, tasks) or where they come from. An agent can guess this lists unread messages, but must infer the resource type from sibling names like send and reply rather than from the description itself.

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?

No when-to-use guidance and no named alternative; the agent is not told how this differs from history (presumably read items) or wait (presumably new-item blocking). The only conditional present is the peek flag, which governs side effects rather than tool selection.

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