phabricator-mcp

phabricator_conpherence_read

Read-only

Read messages from a Conpherence chat room or thread in reverse chronological order, with limit and offset pagination and lookup by room ID or PHID.

Instructions

Read messages from a Conpherence chat room/thread (returned in reverse chronological order). Uses conpherence.querytransaction (the only Conduit method that returns message content).

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

Input Schema

Name	Required	Description
`limit`	No	Maximum messages to return
`offset`	No	Result offset for pagination
`roomID`	No	Numeric room ID (provide this or roomPHID)
`roomPHID`	No	Room PHID (provide this or roomID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.19May 29, 2026

TDQS

A4/5.0

Behavior3/5

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

The readOnlyHint annotation already declares this as a safe read operation. The description adds useful behavioral detail that results are returned in reverse chronological order and that it relies on conpherence.querytransaction, but it does not describe auth requirements, rate limits, or the returned message fields.

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?

Two sentences with the core purpose front-loaded and no wasted text. The implementation note about conpherence.querytransaction is compact and adds useful context without bloating the definition.

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 read/list tool with full parameter schema coverage, a clear read-only annotation, and no output schema, this is nearly complete. The description states ordering but does not describe the message shape, which is a minor omission rather than a blocking gap.

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 all four parameters are already documented structurally. The description adds no parameter-specific syntax or constraints beyond the schema, which is acceptable at the baseline for fully covered schemas.

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?

States a specific verb and resource: reading messages from a Conpherence chat room/thread. This clearly distinguishes it from sibling mutations such as conpherence_create, conpherence_edit, and conpherence_send.

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?

The description gives clear context that this is the read path for Conpherence messages and notes the reverse chronological order. It does not explicitly name alternatives or when-not conditions, but the reading use case is unambiguous against the sibling send/create/edit tools.

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

Deploy Server