Skip to main content
Glama

phabricator_repository_file_content

Retrieve file contents from a Phabricator Diffusion repository by providing a file path and commit hash or branch name. Returns base64-encoded content, or indicates if the file is too large.

Instructions

Read file contents from a Diffusion repository at a given path and commit/branch. Returns the file content as a base64-encoded blob. If the file is too large, returns tooHuge: true with no content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFile path in the repository (e.g., "src/index.ts")
repositoryNoRepository callsign, short name, or PHID
commitYesCommit hash or branch name
branchNoBranch name
timeoutNoQuery timeout in seconds
byteLimitNoMaximum file size in bytes to return
Behavior4/5

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

With no annotations, the description carries full burden. It discloses base64 encoding and large file handling ('tooHuge: true'). Missing details on error handling for invalid paths or permissions, but still adds significant value beyond schema.

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 concise sentences front-loading the purpose and key behavioral details. No fluff or redundancy.

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?

Given no output schema, the description adequately explains the return format and large file behavior. It could include error scenarios, but is largely complete for a straightforward file read tool.

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%, and the description does not add substantial meaning beyond what the parameter descriptions already provide. The mention of 'path and commit/branch' echoes schema fields.

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?

The description clearly states the action (read), resource (file contents), and scope (from Diffusion repository at given path and commit/branch). It is specific and distinguishable from sibling tools like phabricator_repository_browse and phabricator_repository_code_search.

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?

No explicit guidance on when to use this tool versus alternatives. The context is clear enough to infer usage, but no exclusions or when-not-to-use information is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/freelancer/phabricator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server