OwnerRez MCP Server

list_messages

Get all messages from an OwnerRez conversation thread. Filter by date, include drafts or attachments, and set a result cap to manage message history.

Instructions

List the messages in a conversation thread.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "list_messages"
  }
}

Input Schema

Name	Required	Description
`max_items`	No	Safety cap on results.
`since_utc`	No	Only messages on/after this UTC time (ISO-8601).
`thread_id`	Yes	The OwnerRez conversation/thread ID (``threadId``).
`include_drafts`	No	Include unsent draft messages.
`include_attachments`	No	Include attachment URLs.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations, but description only says 'list', implying read-only. Does not mention that it respects include_drafts/include_attachments flags or any side effects. Minimal transparency.

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?

One clear sentence with no redundant words.

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?

Covers the core function, but omits any mention of pagination or default behavior. However, output schema may cover return format. Slightly incomplete but acceptable for a list tool.

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 fully describes all five parameters with descriptions. Description adds no extra meaning beyond mentioning 'conversation thread', which is already in schema. Baseline 3.

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?

Clearly states verb and resource: lists messages in a thread. Distinguishes from other list tools by specifying thread context.

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 mention of when to use this vs alternatives like send_message or list_open_messages. Lacks explicit guidance.

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

Deploy Server