phabricator-mcp

phabricator_conpherence_edit

Destructive

Edit a Conpherence chat room by renaming it, updating its topic, sending a message, and adding or removing participants.

Instructions

Edit a Conpherence chat room/thread. Rename it or manage participants.

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": {
      "objectIdentifier": "<objectIdentifier>"
    },
    "name": "phabricator_conpherence_edit"
  }
}

Input Schema

Name	Required	Description
`title`	No	New room title
`topic`	No	Room topic/description
`comment`	No	Send a message alongside the edit (supports Remarkup)
`objectIdentifier`	Yes	Room monogram (e.g., "Z123"), numeric ID, or PHID
`addParticipantPHIDs`	No	Participant PHIDs to add
`removeParticipantPHIDs`	No	Participant PHIDs to remove

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.19May 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, so safety is partly covered. The description adds that participants can be managed, but does not disclose that removing participants is the destructive aspect, nor mention permissions, reversibility, or the side effect of the 'comment' parameter posting a message.

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 short sentences, front-loaded with the operation and resource, with no filler. It is efficient, though it is arguably under-specified rather than maximally informative.

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 destructive, six-parameter mutation tool with no output schema, the description is thin: it omits the topic and comment parameters and does not warn that participant removal is irreversible. The rich schema partially compensates, but the description should do more about the destructive semantics.

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 all six parameters, including the object identifier formats and Remarkup support, are already documented in the schema. The description only echoes 'rename' and 'participants' and adds no syntax, format, or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Edit') and resource ('Conpherence chat room/thread') and names the two main capabilities (rename, manage participants). It implicitly separates itself from the sibling read/create/send tools by naming the edit operation, though it never references them explicitly.

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?

There is no guidance on when to use this versus phabricator_conpherence_create, phabricator_conpherence_read, or phabricator_conpherence_send. The agent must infer that editing an existing room requires this tool, but nothing states prerequisites or exclusions.

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

Deploy Server