perseus

perseus_inbox

Read-only

View coordination messages from other agents in the workspace inbox. Filter to show only unread messages.

Instructions

Read agent-to-agent messages from the workspace inbox. Use to check for coordination messages from other agents. Filter to unread only. Read-only; returns message array with read/unread status.

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": "perseus_inbox"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of messages to return
`unread`	No	If 'true', show only unread messages

Output Schema

Name	Required	Description	Default
`messages`	No
`unread_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.10Jun 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "messages": {
+      "items": {
+        "properties": {
+          "content": {
+            "description": "Message body",
+            "type": "string"
+          },
+          "id": {
+            "description": "Message identifier",
+            "type": "string"
+          },
+          "read": {
+            "description": "Whether the message has been read",
+            "type": "boolean"
+          },
+          "sender": {
+            "description": "Message sender",
+            "type": "string"
+          },
+          "timestamp": {
+            "description": "ISO-8601 timestamp",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unread_count": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedv1.0.7Jun 10, 2026

changedInput schema / properties / limit / description

Previous value: -"limit= modifier for @inbox"New value: +"Maximum number of messages to return"

changedInput schema / properties / unread / description

Previous value: -"unread= modifier for @inbox"New value: +"If 'true', show only unread messages"

First observedv0.1.0May 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true; the description adds context about the message source (workspace inbox) and return format (message array with read/unread status), going beyond the annotation without contradiction.

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?

The description is three concise sentences, each earning its place: purpose, usage, and key features. It is front-loaded and free of filler.

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

Completeness5/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 two optional parameters and an output schema present, the description covers all essential behavioral details: read-only, message source, filter capability, and return shape. No gaps remain.

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?

Both parameters have full schema descriptions (100% coverage). The description only reinforces the unread parameter with 'Filter to unread only', adding no new meaning beyond the schema. Baseline 3 is appropriate.

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

Purpose5/5

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

Description clearly identifies the tool as reading agent-to-agent messages from the workspace inbox, with a specific use case of checking coordination messages. It distinguishes from siblings by specifying the source (inbox) and context (agent-to-agent).

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

Usage Guidelines4/5

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

Explicitly suggests using the tool to check coordination messages and mentions filtering to unread. While it doesn't specify when not to use it or mention alternatives, the context of sibling tool names like 'perseus_read' provides implicit differentiation.

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