Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_buildable_search

Read-only

Search Harbormaster buildables such as revisions and commits, filtering by IDs, PHIDs, status, or manual/automated type with cursor-based pagination.

Instructions

Search Harbormaster buildables (objects that can be built, like revisions or commits)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "phabricator_buildable_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoCursor for next-page pagination
limitNoMaximum results (max 100)
orderNoResult order
beforeNoCursor for previous-page pagination
queryKeyNoBuilt-in query: "all"
constraintsNoSearch constraints

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.19

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint=true annotation already tells the agent this is a safe read operation. The description adds useful domain context by explaining that buildables are objects that can be built, but it does not disclose pagination behavior, return format, or rate limits. With annotations carrying the safety profile, this is an appropriate partial contribution.

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?

The description is a single, front-loaded sentence with zero waste. It efficiently conveys the core purpose and clarifies the domain term without unnecessary elaboration.

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?

The description is minimally adequate for a search tool with a fully documented schema and a read-only annotation. However, given the large number of sibling search tools, it should ideally clarify when this tool is the right choice and what kind of results it returns, which it does not.

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 six parameters and nested constraints are fully documented in the schema itself. The description does not add any parameter-specific meaning beyond what is already structured, making the baseline score of 3 appropriate.

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 (Search) and resource (Harbormaster buildables), and clarifies what a buildable is with examples (revisions or commits). It does not explicitly differentiate from similarly named siblings like phabricator_build_search, but the resource name is distinct enough for an agent to infer the difference.

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?

The description gives no guidance on when to use this tool versus alternatives such as phabricator_build_search or phabricator_build_target_search. It also states no prerequisites or exclusions, leaving the agent to infer usage context solely from the resource name.

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