Skip to main content
Glama

Flowmails

list_message_states

Read back the agent's own per-message state — the record claim_message and complete_message write. Returns one row per message: its messageId, the state (pending, processing, done or failed), the labels and note the agent attached, who holds the claim and when. The rows belong to the CALLING credential, so another credential of the same tenant does not read them; domainId is required because the state is scoped to the domain whose mailbox received the message. Use it after a restart to find the messages this agent took and never finished: state: "processing" is that list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domainId": "<domainId>"
    },
    "name": "list_message_states"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional: the page size.
stateNoOptional: only the states in this one. `processing` is the list a restarted agent wants — the messages it took and never finished.
domainIdYesThe id of the domain whose mailbox received the messages — from `list_domains`. Required: the state belongs to one domain's mailbox.
messageIdNoOptional: narrow to one message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations present, the description carries the full behavioral burden and does so well: it discloses credential-level scoping ('rows belong to the CALLING credential'), explains why `domainId` is required, lists returned fields, enumerates state values, and gives the key recovery use case.

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 front-loaded, dense, and free of filler. Each sentence contributes: what is read, what is returned, who can see it, why `domainId` is required, and the primary operational use case.

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 list tool with no output schema and no annotations, the description is largely complete: it covers ownership, return fields, state semantics, and the main use case. It is slightly incomplete around pagination/ordering behavior and how `limit` affects results.

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 100%, so the schema already defines all four parameters in detail. The description reinforces the meaning of `state: "processing"` and the domain scope, but adds little parameter syntax or semantics beyond what the schema provides.

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?

The description uses a specific verb and resource — 'Read back the agent's own per-message state' — and explicitly ties it to the records written by `claim_message` and `complete_message`. This distinguishes it from the write-oriented siblings without requiring schema inspection.

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?

It gives a concrete usage scenario: after a restart, use `state: "processing"` to find messages taken and never finished. It implicitly contrasts this with `claim_message` and `complete_message`, but does not explicitly state when not to use it or name other read alternatives.

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.

Resources