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

hex-dashboard-mcp

by richardggxcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_projects

Find and list Hex projects in the workspace. Filter by name substring to get project IDs, names, and app URLs for use with other tools.

Instructions

List Hex projects in the workspace. Optionally filter by name substring. Returns project IDs, names, and app URLs needed for other tools.

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": "list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and accurately states the read-only listing behavior and returned fields. It does not disclose limit semantics, ordering, or edge cases, but for a simple list operation this is acceptable though not rich.

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?

Two short sentences, front-loaded with the main action, and no filler. Every sentence adds value: the first states scope, the second explains optional filtering and return value relevance.

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

Completeness4/5

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

The description is complete for a simple list tool, especially with an output schema already covering return structure. It adds the key context that returned IDs/URLs are needed for other tools, but does not mention the meaning of 'limit' or pagination behavior.

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 0%, so the description must compensate. It explains 'search' as a name substring filter, which is helpful, but 'limit' is only recognizable from its name/schema default and is not described in text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses a specific verb ('List') and resource ('Hex projects in the workspace'), clearly indicating a collection operation. It distinguishes from siblings like get_project by emphasizing plural projects and returning IDs/URLs for use by other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: when you need project IDs, names, or app URLs for other tools, and optionally filtering by name substring. However, it does not explicitly contrast with get_project or state when not to use it.

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