user-review-mcp

by wtfsayo

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

get-user-review

Get critical user feedback on completed work to identify issues and confirm requirements are met.

Instructions

Get a user review of the work that was completed.

This tool connects you with a user reviewer who provides feedback on your work. It helps ensure quality and catches potential issues.

When to use this tool:

After completing a significant piece of work
When you need feedback on your approach
To validate that your implementation meets requirements

The review will provide honest, critical feedback to help improve the work.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workDescription": "<workDescription>"
    },
    "name": "get-user-review"
  }
}

Input Schema

Name	Required	Description	Default
`workDescription`	Yes	A description of what work was completed that needs review
`context`	No	Optional additional context about the work

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.7Jun 17, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Without annotations, the description should disclose behavioral traits. It hints that the tool provides 'honest, critical feedback' and implies a human reviewer, but it doesn't specify whether the review is synchronous, if there are delays, or any required permissions. The description is vague about the mechanics.

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 description is moderately concise with multiple sentences and a bulleted list. Each part adds value, but it could be tightened without losing meaning. Not excessively long, but not extremely efficient.

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?

Missing important details: no mention of what the tool returns (string, object, etc.), whether the review is instant or queued, or any prerequisites. With 2 parameters and no output schema, the description should cover these aspects for completeness.

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 coverage is 100% with clear descriptions for both parameters. The tool description adds usage context (e.g., 'after significant work') but doesn't significantly enhance parameter understanding beyond the schema. Baseline 3 for high coverage.

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?

The description clearly states the tool's action ('Get a user review') and resource ('the work that was completed'). It also elaborates on the purpose: connecting with a user reviewer for feedback on work. No sibling differentiation needed as no siblings are listed.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use the tool with three bullet points (after completing significant work, when needing feedback, to validate implementation). It lacks explicit when-not-to-use or alternatives, but given no siblings, this is sufficient.

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

get-user-reviewA