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

hex-mcp-server

by chuotdelongchamp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hex-get-project

Fetch detailed metadata for a single Hex project by ID, optionally including sharing details, to audit or inspect workspace projects.

Instructions

Get detailed metadata for a single Hex project by ID.

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>"
    },
    "name": "hex-get-project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe Hex project UUID
includeSharingNoInclude sharing metadata (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/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. 'Get detailed metadata' implies a read, but nothing is said about required permissions, what 'detailed metadata' actually contains, whether includeSharing has access implications, or any rate limits.

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. It is efficient, though arguably too terse for a tool with an undocumented return shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool this is minimally viable, but with no annotations and no output schema the description is the only place the return contents ('detailed metadata') could be clarified, and it stays vague.

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 description coverage is 100%, so both parameters are already documented in the schema. The description adds only the 'by ID' framing for projectId and says nothing about the includeSharing flag, so the baseline 3 is appropriate.

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 (Hex project metadata) scoped to a single record by ID, which separates it from hex-list-projects and hex-get-project-runs. It does not, however, explicitly name or contrast with any sibling tool.

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 when-to-use or when-not-to-use guidance, no mention of alternatives such as hex-list-projects or hex-update-project, and no prerequisites. The 'by ID' phrasing only weakly implies a single-record lookup.

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