Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_conpherence_create

Creates a Conpherence room in Phabricator with a title, optional topic, initial message, and participant PHIDs, automatically adding the caller as a participant.

Instructions

Create a Conpherence room; you are always a participant.

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": {
      "title": "<title>"
    },
    "name": "phabricator_conpherence_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesThread title
topicNoRoom topic/description
messageNoInitial message (supports Remarkup)
participantPHIDsNoOther participants' PHIDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / participantPHIDs / description
      Previous value: -"Participant user PHIDs to add"New value: +"Other participants' PHIDs"
  2. First observedv2.0.19

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered. The description adds a genuinely useful behavioral fact — the caller is always included as a participant — but says nothing about required permissions, whether the returned room ID is needed downstream, or what happens with duplicate titles.

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?

A single tight sentence with no filler, front-loaded with the action. It is efficient, though the brevity comes partly from omitting useful detail rather than from ruthless editing.

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 four-parameter mutation tool with full schema coverage and no output schema, the description covers the core action and one behavioral trait. It leaves open whether the new room is returned/identifiable and any precondition on participant PHIDs, which an agent would benefit from knowing.

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 (title, topic, message, participantPHIDs) are already documented. The description adds no syntax, format, or constraint detail beyond the schema, so the 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?

The description states a specific verb and resource ("Create a Conpherence room"), which clearly distinguishes it from read/edit/send siblings in the same family. It stops short of explicitly contrasting with those siblings, but the verb alone is unambiguous.

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 guidance on when to create a room versus editing an existing one, or when to prefer sending a message via phabricator_conpherence_send. The only contextual hint is the participant-membership note, which is not usage routing.

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

Deploy Server

Other Tools