phabricator-mcp

phabricator_user_search

Read-only

Search Phabricator users by name, username, ID, status, or full-text query, with filters for admin, bot, MFA, and approval state. Supports pagination.

Instructions

Search Phabricator users

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

Input Schema

Name	Required	Description
`after`	No	Cursor for next-page pagination
`limit`	No	Maximum results (max 100)
`order`	No	Result order
`before`	No	Cursor for previous-page pagination
`queryKey`	No	Built-in query: "all", "active", "approval"
`attachments`	No	Data attachments
`constraints`	No	Search constraints

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.19May 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations declare `readOnlyHint: true`, so safety is already communicated. The description adds nothing about pagination behavior, return shape, result limits, or search semantics beyond the schema. With annotations covering the safety profile, the description still contributes no behavioral context.

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?

The description is extremely short and front-loaded, with no wasted words. However, its brevity borders on under-specification rather than efficient communication. It could include one useful sentence of routing or usage context without becoming verbose.

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?

This is a search tool with seven optional parameters, nested constraint filters, pagination controls, and no output schema. The description does not explain default behavior, how to combine filters, what results look like, or when to prefer this over `phabricator_user_whoami`. The rich schema helps, but the description leaves significant contextual gaps for 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 all seven parameters, including the nested `constraints` object and `queryKey` enum-like values, are documented in the schema itself. The description adds no parameter meaning beyond the schema. A baseline 3 is appropriate 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.

Purpose4/5

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

The description states a specific verb and resource: 'Search Phabricator users'. An agent can understand the tool's basic function. However, it does not distinguish this search tool from the sibling `phabricator_user_whoami`, which is the other user-related lookup tool.

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 offers no guidance on when to use this tool versus `phabricator_user_whoami` or other search tools. There are no stated preconditions, exclusions, or recommended scenarios. An agent must infer usage entirely from the name.

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

Deploy Server