hex-mcp-server

hex-list-suggestions

List context suggestions from Hex workspaces with pagination and status filters to review open, completed, resolved, in-progress, or dismissed items.

Instructions

List context suggestions (paginated, filterable by status).

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": "hex-list-suggestions"
  }
}

Input Schema

Name	Required	Description	Default
`after`	No
`limit`	No
`sortBy`	No
`status`	No
`sortDirection`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 28, 2026

TDQS

C2.7/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 discloses pagination and status filtering, but says nothing about ordering defaults, result volume, permissions, or what a returned suggestion contains (no output schema either).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is efficient. However, the terseness is achieved partly by omitting the parameter detail this tool needs, so compactness shades into under-specification.

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?

For a 5-parameter tool with zero schema descriptions, no annotations, and no output schema, the description covers only pagination and status filtering. Three sort/pagination parameters and the return shape are left for the agent to guess.

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% across 5 parameters, and the description only alludes to two of them (pagination via 'paginated', status via 'filterable by status'). The enum values for status, sortBy, and sortDirection and the meaning of 'after' are left entirely undocumented.

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+resource ('List context suggestions') and adds scope qualifiers (paginated, filterable by status). It does not distinguish itself from siblings such as hex-get-suggestion or hex-update-suggestion, but the read-only listing intent is unambiguous.

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?

No indication of when to use this versus hex-get-suggestion (single-record fetch) or the update/review siblings. The parenthetical hints at supported operations but offers no selection guidance or prerequisites.

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

Deploy Server