Skip to main content
Glama
mcp-hangar

mcp-hangar

by mcp-hangar

hangar_details

Retrieve configuration and runtime info for an MCP server or group: health history, state, mode, tool schemas, and group membership. Get the details you need for monitoring and troubleshooting.

Instructions

Get configuration and runtime info for a mcp_server or group.

    CHOOSE THIS when: you need mcp_server config, health history, or group membership.
    CHOOSE hangar_tools when: you need tool schemas for invoking.
    CHOOSE hangar_status when: you need quick overview of all mcp_servers.

    Side effects: None (read-only).

    Args:
        mcp_server: str - McpServer ID or Group ID

    Returns:
        McpServer: {
            mcp_server: str,
            state: str,
            mode: str,
            alive: bool,
            tools: [{name, description, inputSchema}],
            health: {consecutive_failures: int, last_check: str, ...},
            idle_time: float,
            meta: object
        }
        Group: {
            group_id: str,
            description: str,
            state: str,
            strategy: str,
            min_healthy: int,
            healthy_count: int,
            total_members: int,
            is_available: bool,
            circuit_open: bool,
            members: [{id, state, in_rotation, weight, priority, consecutive_failures}]
        }
        Error: ValueError with "unknown_mcp_server: <id>"

    Example:
        hangar_details("math")
        # {"mcp_server": "math", "state": "ready", "mode": "subprocess",
        #  "alive": true, "tools": [...], "health": {"consecutive_failures": 0},
        #  "idle_time": 12.5, "meta": {}}

        hangar_details("llm-group")
        # {"group_id": "llm-group", "state": "ready", "strategy": "round_robin",
        #  "healthy_count": 2, "total_members": 3, "members": [...]}

        hangar_details("unknown")
        # Error: unknown_mcp_server: unknown
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcp_serverYes
Behavior4/5

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

No annotations are present, so the description carries the full burden. It explicitly states 'Side effects: None (read-only)' and discloses error behavior (ValueError with 'unknown_mcp_server'). While it could mention more about runtime or network behavior, the provided transparency is solid for a read-only config retrieval.

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?

The description is well-structured with clear sections: purpose, usage guidance, side effects, args, returns, and examples. Every sentence contributes real value, and examples for both return types and error case make it actionable. Length is justified.

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

Completeness5/5

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

Given the tool's complexity (two possible return shapes, error handling) and lack of output schema, the description fully enumerates return fields for both McpServer and Group, plus error cases. Examples cover all scenarios, making it complete enough for an agent to understand outcomes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description compensates by explaining that mcp_server accepts 'McpServer ID or Group ID', and provides concrete examples ('math' as server, 'llm-group' as group). This adds meaning beyond the raw schema, though it could elaborate on how to identify valid IDs.

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?

The description explicitly states 'Get configuration and runtime info for a mcp_server or group', using a specific verb and resource. It clearly distinguishes from siblings by naming hangar_tools and hangar_status as alternatives, leaving no ambiguity about what this tool does.

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

Usage Guidelines5/5

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

The 'CHOOSE THIS when' section provides explicit conditions for using this tool, and it explicitly names alternatives (hangar_tools for tool schemas, hangar_status for quick overview) when not to use it. This is model usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcp-hangar/mcp-hangar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server