Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_revision_paths

Read-only

Retrieves changed file paths for a Differential revision using its numeric ID, returning an array of path strings.

Instructions

Get the list of changed file paths for a Differential revision. Returns an array of file path strings.

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": {
      "revision_id": "<revision_id>"
    },
    "name": "phabricator_revision_paths"
  }
}

Input Schema

NameRequiredDescriptionDefault
revision_idYesNumeric revision ID (e.g., 123). Do not include the "D" prefix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.19

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuinely useful context the annotation cannot: the return shape (array of file path strings), which matters since there is no output schema. It stops there — no note on ordering, whether deleted/added files are distinguished, or behavior for an empty diff — so credit is moderate.

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 purpose and followed by the return type; no filler or redundancy. It is efficient but very sparse, leaving no room for the usage guidance that would make it more than minimal.

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 one-parameter read-only lookup, the definition covers what it does, what it returns, and the annotation covers safety. The absence of an output schema is compensated by the explicit 'array of file path strings' statement. Only edge-case behavior and call-site guidance are missing.

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?

With a single parameter and 100% schema description coverage, the schema already carries the important detail (numeric ID, no 'D' prefix). The description contributes nothing about the parameter, 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 ('Get') and resource ('changed file paths for a Differential revision'), which is easily distinguished from siblings like phabricator_diff_raw (diff content) or phabricator_revision_search (revision metadata). It doesn't explicitly name a sibling to differentiate from, but the resource is narrow enough that no ambiguity remains.

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 when-to-use guidance at all: nothing says to call this before phabricator_diff_raw to enumerate files, nor any prerequisite (e.g., needing a revision ID obtained from revision_search). The use case is only implied by the noun phrase 'changed file paths'.

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