Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_project_search

Read-only

Search and filter Phabricator projects by name, status, members, or custom constraints to locate relevant projects for reporting and workflow automation.

Instructions

Search Phabricator projects

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_project_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoCursor for next-page pagination
limitNoMaximum results (max 100)
orderNoResult order
beforeNoCursor for previous-page pagination
queryKeyNoBuilt-in query: "all", "active" (non-archived), "joined", "watching"
attachmentsNoData attachments
constraintsNoSearch constraints

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.19

TDQS

C2.5/5.0
Behavior2/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. Beyond that, the description adds nothing: no mention of pagination via cursors, result ordering, permission scoping, or the effect of attachments/constraints. For a tool with nested objects and page cursors, this is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is front-loaded and free of waste, but it is under-specified rather than concise for a 7-parameter paginated search with over twenty nested constraint fields. Brevity here does not earn its place against the tool's complexity.

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?

Given nested constraint objects, cursor pagination, no required parameters, no output schema, and no annotation beyond read-only, the description leaves an agent to reconstruct the entire usage model from the schema. It is not complete enough to guide correct invocation.

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 every parameter including the nested constraints and attachments objects is documented in the schema. The description contributes no added meaning, which matches the baseline 3 when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ("Search Phabricator projects"), which distinguishes it by domain from siblings like phabricator_task_search or phabricator_project_edit. However, it is essentially a restatement of the tool name and says nothing about search scope, filters, or what kind of project listing is returned.

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 guidance on when to use this versus the many sibling search tools, nor any mention of prerequisites, pagination expectations, or the presence of built-in queries. An agent must infer all of that from the schema alone.

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