Loading ToolBench

Reading the current corpus…

mcp-revisor-server MCP server · F · ToolBench

mcp-revisor-server

github.com/mikhael-abdallah/mcp-revisor-server

MCP server for Azure DevOps pull request review automation, providing tools to retrieve pull request diffs and create thread comments on specific lines

2026-07-28+STREAMABLE_HTTP2 tools

35/100

Definition Quality34

Protocol Readiness65

Supportability18

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: Streamable HTTP

Current-spec patterns detected

Summary

Two tools with basic schemas and minimal descriptions. Tool names lack action verbs (should be 'get_pull_request_diff', 'create_thread_comment'). Parameters have types but lack depth. No output schema documented. No error handling guidance. No parameter constraints (enums, ranges). Secrets (AZURE_PAT) exposed in environment but not validated in tool layer. No idempotency hints for write operation.

Tools (2)

Create thread commentwriteauthsource verified35/100

Create thread comment

Get pull request diffread onlyauthsource verified33/100

Get pull request diff

Issues (5)

CRITICALtool-description ↗

Tool descriptions are under 20 characters ('Get pull request diff', 'Create thread comment'). LLMs cannot determine when/why to select tools without substantive descriptions.

Get pull request diffCreate thread comment

HIGHtool ↗

Tool names do not start with action verbs. 'Get pull request diff' should be 'get_pull_request_diff'; 'Create thread comment' should be 'create_thread_comment'. Verb-noun naming lets LLMs parse intent from the name alone.

Get pull request diffCreate thread comment

HIGHresponse-shaper ↗

No output schema documented. LLMs cannot plan downstream calls or extract structured data. Both tools return generic text responses without field definitions.

Get pull request diffCreate thread comment

HIGHrecovery-guide ↗

No error handling guidance. Errors from Azure API calls (getPullRequestInfo, createThreadComment) are not caught with actionable recovery messages. LLMs receive raw errors with no next-step guidance.

Recommendations

Expand tool descriptions to 50-200 characters. Example: 'Get pull request diff' → 'Retrieve the unified diff between source and target branches of an Azure DevOps pull request. Returns file paths, line numbers, and changes. Use this to review code changes before commenting.'
Rename tools to verb_noun format: 'get_pull_request_diff' and 'create_thread_comment'. This matches production baselines and aids LLM intent parsing.
Add parameter descriptions with format constraints. Example: pullRequestUrl → 'Azure DevOps pull request URL (format: https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{id})'.
Document output schemas explicitly. Example: get_pull_request_diff returns {diff: string, file_count: number, lines_changed: number}. create_thread_comment returns {success: boolean, thread_id: string, created_at: string}.
Wrap Azure API calls in try-catch with actionable error messages. Example: 'Pull request not found. Verify the URL is correct and you have access to the repository.' instead of raw HTTP errors.

Score history

Overall score trend

First recorded score · v2 rubric

35/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	35	2026-07-28+	v2