Skip to main content
Glama

mailbox

by bot.mailbox
OverviewDiscussionsAdmin

list_facility_conversations

Read-onlyIdempotent

List your conversation with your mailbox facility, including its unread message count and last message preview. Facility routing is automatic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of conversations to return (1-100). Defaults to 20.
offsetNoNumber of conversations to skip for pagination. Defaults to 0.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesFacility conversations plus pagination.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": true,
+      "description": "Facility conversations plus pagination.",
+      "properties": {
+        "conversations": {
+          "description": "Facility conversation summaries.",
+          "items": {
+            "additionalProperties": true,
+            "description": "One returned record.",
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "pagination": {
+          "additionalProperties": false,
+          "description": "Pagination metadata for the current result set.",
+          "properties": {
+            "has_more": {
+              "description": "Whether another page is available.",
+              "type": "boolean"
+            },
+            "limit": {
+              "description": "Maximum records requested.",
+              "type": "integer"
+            },
+            "offset": {
+              "description": "Records skipped before this page.",
+              "type": "integer"
+            },
+            "total": {
+              "description": "Total matching records when available.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "conversations",
+        "pagination"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds almost no behavioral context beyond that—no mention of pagination behavior (beyond the schema), sorting, or what 'conversation' contains. Since an output schema exists, return details are less critical, but the description still contributes little.

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 sentences, front-loaded with the action, and no filler. The second sentence about automatic routing is somewhat cryptic but short. Efficient overall.

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 simple list tool with 2 optional params, full schema coverage, annotations, and an output schema, the description covers the basics. However, the ambiguous phrase 'mailbox facility' and lack of sibling differentiation leave gaps in an environment with many similar-sounding list/get tools.

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 coverage is 100%, so the two parameters (limit, offset) are already fully documented in the schema. The description adds no parameter meaning at all. Baseline 3 applies when the schema does the heavy lifting with high coverage.

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?

The description states a verb (list) and resource (facility conversations), but 'your mailbox facility' is jargon that doesn't clearly map to a concrete resource, and it doesn't distinguish this tool from siblings like get_facility_messages or list_postal_threads. The purpose is vaguely inferable but not precise enough for confident selection.

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 guidance is given on when to use this tool versus alternatives. With siblings such as get_facility_messages and list_postal_threads, an agent has no signal about which to pick. The note 'Facility routing is automatic' does not address when-to-use.

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

All mailbox toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources