Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_column_search

Read-only

Search project workboard columns by column IDs, PHIDs, or project PHIDs and page through results using cursor and limit parameters.

Instructions

Search project workboard columns

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_column_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

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds nothing else: no mention of pagination behavior, default result set when no constraints are supplied, or the fact that constraints are ANDed/nested. For a 6-parameter search with a nested constraints object, that is a thin disclosure.

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 single phrase is front-loaded and wastes no words, but for a tool with six parameters and a nested constraint object it is arguably under-specified rather than genuinely concise. Nothing is misordered; there is simply very little content.

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 a nested constraints object, cursor pagination (after/before), and no output schema, the description leaves important context unstated: whether an empty search returns all columns, how projects scope the result, and what a column object contains. The schema covers parameter shapes, but the operational picture is incomplete.

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 ids/phids/projects constraints is documented in the schema itself. The description contributes no additional semantics, which is the expected baseline-3 case 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?

States a specific verb and resource: 'Search project workboard columns.' An agent can tell this is a read/query tool for workboard column objects, distinct from phabricator_project_search (projects) or phabricator_task_search. It stops short of explicitly naming those siblings or clarifying the project-vs-column relationship, so it is clear but not fully differentiated.

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 when-to-use guidance, no mention of prerequisites (e.g. that a project PHID is typically needed to scope results), and no reference to any alternative tool. The agent must infer usage entirely from the name and schema.

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