Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_document_add_comment

Adds a comment to a Phriction wiki document by slug, PHID, or ID; supports Remarkup for formatted discussion and feedback.

Instructions

Add a comment to a Phriction wiki document

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>",
      "comment": "<comment>"
    },
    "name": "phabricator_document_add_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesComment text (supports Remarkup)
objectIdentifierYesDocument slug, PHID, or ID (e.g., "projects/myproject/")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.19

TDQS

B3.1/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description should carry the weight for what a comment mutation does. It says nothing about whether the comment is appended to the document timeline, whether it triggers notifications/subscriptions, what permissions are needed, or whether the text is processed as Remarkup (the schema mentions Remarkup, not the description).

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 front-loaded sentence with no filler. It is compact, though the compactness reflects under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema, the description omits what is returned (comment ID, transaction PHID), whether the call fails on a nonexistent document, and any side effects. The rich schema offsets some risk, but an agent still lacks enough to call this confidently in ambiguous cases.

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% with only two params, both documented (comment as Remarkup text, objectIdentifier accepting slug/PHID/ID with an example), so baseline 3 applies. The description adds no parameter meaning of its own beyond naming the resource.

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 (add) and resource (comment) plus the scoping target (Phriction wiki document), which implicitly separates it from the task/blog-post add_comment siblings. It never names those siblings or explains the containment relationship explicitly, so differentiation is inferential rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: you call this to comment on an existing wiki document. There is no guidance on prerequisites (document must exist, edit permission required) and no mention of the sibling comment tools for tasks or blog posts to route the agent away.

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