Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_diff_raw

Read-only

Retrieve raw diff or patch content for a Differential diff by ID. Resolve a revision to its diff ID with the diff search tool first.

Instructions

Get the raw diff/patch content for a Differential diff by diff ID. Use phabricator_diff_search to find the diff ID from a revision PHID first.

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": {
      "diffID": "<diffID>"
    },
    "name": "phabricator_diff_raw"
  }
}

Input Schema

NameRequiredDescriptionDefault
diffIDYesThe diff ID (numeric, e.g., 1392561). Use phabricator_diff_search to find this from a revision.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.19

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that the return is raw patch text, which is genuinely useful context, but it says nothing about output size, truncation, or formatting—relevant for a payload that can be very large.

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 short sentences, zero waste, with the core action front-loaded and the prerequisite second. Nothing to trim.

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 single-parameter read tool with readOnlyHint annotations and no output schema, the description states both what goes in and what comes back (raw diff/patch text). Only size/truncation behavior is missing, which is a minor gap at this complexity.

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% and the single diffID parameter already documents its numeric form and the search-first workflow, so the description adds essentially nothing beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific verb and resource ('Get the raw diff/patch content for a Differential diff') and is clearly distinguishable from the sibling phabricator_diff_search, which returns IDs rather than content. An agent can pick between them without opening either schema.

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?

Explicitly states the prerequisite workflow: use phabricator_diff_search to resolve the diff ID from a revision PHID first. It gives clear context but does not say when NOT to use this tool (e.g., for large diffs or when only metadata is needed).

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