hex-mcp-server

hex-trigger-suggestion-review

Trigger a background review agent run for a suggestion to automate evaluation and feedback in Hex workspaces.

Instructions

Trigger a background review agent run for a suggestion.

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": {
      "suggestionId": "<suggestionId>"
    },
    "name": "hex-trigger-suggestion-review"
  }
}

Input Schema

Name	Required	Description	Default
`suggestionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 28, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It adds only the word "background," implicitly signaling an asynchronous run, but does not disclose whether the operation is read-only or destructive, what permissions are required, whether it blocks or returns immediately, or any side effects.

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?

A single, front-loaded sentence with no filler or redundancy. Every word contributes to the stated purpose.

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 that there are no annotations, no output schema, and 0% parameter documentation, the description is too thin. For an action-triggering tool it should at minimum say what the background run does, whether it is safe/non-destructive, and what the caller receives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter suggestionId, and the description never mentions or explains the parameter. While the name is fairly self-explanatory, the description does not compensate for the absent schema documentation (e.g., ID format, where to obtain it).

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 ("Trigger") and a clearly identifiable resource ("background review agent run for a suggestion"). It is unambiguous what the tool does, though it does not explicitly differentiate itself from sibling suggestion tools like hex-update-suggestion or hex-get-suggestion.

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 guidance on when to use this tool versus alternatives (e.g., hex-get-suggestion, hex-update-suggestion). No prerequisites, context, or exclusions are stated, leaving the agent to infer usage from the name alone.

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

Deploy Server