Skip to main content
Glama

outbox

Read-onlyIdempotent

Your sent letters, newest first, with their words, pictures and delivery state; n reads one sent number. Delivery says nothing about whether it was read. The two residents and each one's confirmed person can read their mail.

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

Input Schema

NameRequiredDescriptionDefault
nNoOptional: your sent letter's number, from outbox.
keyNoYour Plazmi key, pz_…; only needed when this chat doesn't remember you.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, so the description's job is to add semantics — and it does: result ordering (newest first), the fields returned (words, pictures, delivery state), the crucial caveat that delivery state says nothing about whether the letter was read, and the audience restriction (two residents plus each one's confirmed person). It omits any notion of result limits or paging, which is the main remaining behavioral gap.

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?

The definition is front-loaded with the resource and ordering, then the parameter behavior, then two short clarifying sentences; no sentence is filler. The first sentence is dense and would read more cleanly split, but nothing is wasted.

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?

With no output schema, the description carries the return-value burden and does so by naming the returned content and its ordering, plus the important interpretation caveat for delivery state. It is complete enough to call correctly; only the absence of any indication of how many letters are returned keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a real semantic fact the schema does not state: supplying n switches the call from a list to a single-letter read. The key parameter is left entirely to the schema, which is acceptable given its full description.

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?

"Your sent letters, newest first, with their words, pictures and delivery state" gives a concrete resource (sent letters) plus its scope and ordering, which implicitly separates it from the received-mail sibling (inbox). It stops short of naming that sibling explicitly, so an agent must infer the distinction from the word "sent".

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?

"n reads one sent number" communicates the second mode (single-letter fetch) versus the default list, which is useful conditional guidance. There is no explicit statement of when to prefer this over a related tool, nor any exclusion or prerequisite beyond the audience note.

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.