Skip to main content
Glama
Sign In
hex-mcp-server

hex-mcp-server

by chuotdelongchamp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hex-get-run-status

Retrieve the current status of a specific Hex project run by providing its project and run IDs.

Instructions

Get the status of a specific project run.

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": {
      "projectId": "<projectId>",
      "runId": "<runId>"
    },
    "name": "hex-get-run-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

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, yet it discloses nothing beyond the basic read action. It does not say whether this must be polled, what status values are returned, whether terminal states are reflected, or what auth/scope is required. For a status-lookup tool this is a notable gap.

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?

One clean, front-loaded sentence with no filler. It is appropriately sized, though its brevity comes at the cost of the missing details noted elsewhere.

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?

No output schema, no annotations, and no parameter documentation, so the description should carry more of the load than it does. The agent gets no idea of the response shape (status enum, timestamps) or polling expectations for a run-status lookup.

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 both required parameters, and the description adds no clarification of projectId vs runId, their formats, or where to obtain them. With two undocumented required params, the description fails to compensate for the coverage gap.

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 (get) and resource (status of a specific project run), so the agent can tell it is a read of one run's state rather than a list or an execution trigger. It does not differentiate itself from close siblings such as hex-get-project-runs or hex-run-project, but the purpose itself 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 when-to-use guidance, no mention of alternatives (e.g., hex-get-project-runs for enumerating runs, hex-cancel-run for stopping one), and no stated prerequisites such as needing a run to be in progress. Usage must be entirely inferred from the name.

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