hex-mcp-server

hex-edit-group

Update a Hex workspace group's name and add or remove members.

Instructions

Edit a group (name, members).

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": {
      "groupId": "<groupId>"
    },
    "name": "hex-edit-group"
  }
}

Input Schema

Name	Required	Description
`name`	No
`groupId`	Yes
`members`	No	{ add: { users: [...] }, remove: { users: [...] } }

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 28, 2026

TDQS

C2.6/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, but it says nothing about permissions, whether edits are partial or replace existing state, or what happens to members not mentioned. For a mutation tool with zero annotation coverage this is a significant gap — only the word 'Edit' hints at mutation.

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?

A single short sentence with no waste and the resource front-loaded, which is structurally sound. Its brevity edges into under-specification rather than genuine conciseness given the tool's complexity.

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?

A mutation tool with no annotations, no output schema, nested object parameters, and 33% schema coverage needs considerably more context than one sentence. The agent lacks enough information about partial-update behavior and the nested members payload to invoke this confidently.

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 only 33%, so the description should compensate, and it does name the two optional fields. However, it never explains that 'members' takes a nested {add:{users},remove:{users}} structure, nor that groupId is required, so the semantic gap over the schema remains large.

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 and resource ('Edit a group') and enumerates the editable fields (name, members), which separates it from siblings like hex-create-group, hex-delete-group, and hex-get-group. It does not explicitly name an alternative, but the 'edit' verb plus field list makes the operation 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 guidance on when to use this versus hex-create-group, hex-delete-group, or the other sharing-edit tools, and no prerequisites or permission notes. The agent must infer usage entirely from the verb.

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

Deploy Server