Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_audit_query

Read-only

Search commit audit requests by status, auditor, or commit PHIDs through the legacy audit query endpoint, enabling audit-specific filtering unavailable in modern commit search.

Instructions

Search commit audit requests using the legacy audit.query endpoint. For most use cases, prefer phabricator_commit_search with the auditors attachment. This frozen endpoint provides audit-specific status filtering not available in the modern API.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (max 100)
offsetNoResult offset for pagination
statusNoAudit status filter: "audit-status-any" (default), "audit-status-open", "audit-status-concern", "audit-status-accepted", "audit-status-partial"
commitPHIDsNoCommit PHIDs to check audit status for
auditorPHIDsNoAuditor user/project PHIDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.19

TDQS

A4.4/5.0
Behavior4/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 genuinely useful context the annotations don't: this endpoint is "frozen"/legacy, meaning it is stable but will not evolve and should not be the default choice. It doesn't describe pagination behavior or return shape, but pagination is documented in the 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?

Three tight sentences: what it does, the preferred alternative, and why this one still exists. The routing guidance is front-loaded immediately after the purpose statement, so an agent that stops reading early still lands on the right tool.

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?

For a read-only, zero-required-parameter search tool with a fully documented schema and readOnlyHint annotation, the description covers the decision-relevant facts: purpose, alternative, and legacy status. Output format and pagination are the only omissions, and both are low-risk here.

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 enumerated status values is already documented. The description's reference to "audit-specific status filtering" confirms the status parameter's purpose but adds no syntax or semantics beyond the schema, so the baseline applies.

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?

States a specific verb and resource ("Search commit audit requests") and names the endpoint backing it (legacy audit.query). It explicitly separates itself from the sibling phabricator_commit_search, so an agent can pick between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit default routing rule ("For most use cases, prefer phabricator_commit_search with the auditors attachment") plus the exact condition that selects this tool instead: audit-specific status filtering unavailable in the modern API. Both the when and the when-not are present.

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