Skip to main content
Glama
dmarsters

Constellation Composition MCP Server

by dmarsters

Get Server Info and Capabilities

get_server_info
Read-onlyIdempotent

Retrieve server metadata, capabilities, and status to understand available tools, parameter dimensions, states, presets, and visual vocabulary for constellation-based image generation.

Instructions

Get server metadata, capabilities, and Phase 2.6/2.7 status.

Layer 1: Pure reference (0 tokens).

Returns comprehensive information about the constellation composition server including available tools, parameter space dimensions, canonical states, rhythmic presets, and visual vocabulary types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function `get_server_info` provides comprehensive server metadata, capabilities, and status regarding available constellations, rhythmic presets, and visual types.
    # ============================================================================
    # PHASE 2.6 / 2.7 MCP TOOLS
    # ============================================================================
    
    @mcp.tool(
        name="get_server_info",
        annotations={
            "title": "Get Server Info and Capabilities",
            "readOnlyHint": True,
            "destructiveHint": False,
            "idempotentHint": True,
            "openWorldHint": False
        }
    )
    async def get_server_info() -> str:
        """
        Get server metadata, capabilities, and Phase 2.6/2.7 status.
    
        Layer 1: Pure reference (0 tokens).
    
        Returns comprehensive information about the constellation composition
        server including available tools, parameter space dimensions, canonical
        states, rhythmic presets, and visual vocabulary types.
        """
        info = {
            "server": "constellation_composition_mcp",
            "description": "Maps astronomical constellation patterns to compositional "
                           "parameters, rhythmic dynamics, and image generation prompts",
            "version": "2.7.0",
            "constellations_available": len(CONSTELLATIONS),
            "parameter_space": {
                "dimensions": len(CONSTELLATION_PARAMETER_NAMES),
                "parameters": CONSTELLATION_PARAMETER_NAMES,
                "bounds": [0.0, 1.0],
                "canonical_states": len(CONSTELLATION_CANONICAL_STATES)
            },
            "phase_1a_trajectory": {
                "enabled": True,
                "method": "cosine_interpolation",
                "tools": ["compute_constellation_trajectory"]
            },
            "phase_2_6_rhythmic": {
                "enabled": True,
                "presets": {
                    name: {
                        "period": cfg["steps_per_cycle"],
                        "pattern": cfg["pattern"],
                        "states": f"{cfg['state_a']} ↔ {cfg['state_b']}"
                    }
                    for name, cfg in CONSTELLATION_RHYTHMIC_PRESETS.items()
                },
                "all_periods": sorted(set(
                    p["steps_per_cycle"] for p in CONSTELLATION_RHYTHMIC_PRESETS.values()
                )),
                "tools": ["list_constellation_presets", "apply_constellation_preset"]
            },
            "phase_2_7_visualization": {
                "enabled": True,
                "visual_types": list(CONSTELLATION_VISUAL_TYPES.keys()),
                "visual_type_count": len(CONSTELLATION_VISUAL_TYPES),
                "prompt_modes": ["composite", "split_keywords", "descriptive"],
                "tools": ["generate_constellation_attractor_prompt"]
            },
            "tier_4d_composition": {
                "compatible": True,
                "domain_id": "constellation",
                "tools": ["get_constellation_coordinates",
                          "get_constellation_domain_registry_config"]
            }
        }
        return json.dumps(info, indent=2)
Behavior4/5

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

Annotations already cover key behavioral traits (read-only, non-destructive, idempotent, closed-world), but the description adds valuable context beyond this. It specifies the tool returns 'comprehensive information' including 'available tools, parameter space dimensions, canonical states, rhythmic presets, and visual vocabulary types,' which helps the agent understand the scope and format of the response without contradicting annotations.

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 highly concise and well-structured, with two sentences that efficiently convey the tool's purpose and return details. The first sentence states the core function, and the second elaborates on the response content, with no wasted words or redundancy.

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 (server metadata query), rich annotations, and the presence of an output schema, the description is complete enough. It clearly explains what the tool does and what information it returns, without needing to detail parameters or output values, as these are covered by the structured data.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4 as no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's output and purpose, which aligns with the empty input schema.

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 clearly states the tool's purpose with specific verbs ('Get server metadata, capabilities, and Phase 2.6/2.7 status') and resources ('constellation composition server'). It distinguishes itself from siblings by focusing on server-level information rather than constellation-specific operations like 'get_constellation_coordinates' or 'list_all_constellations'.

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

Usage Guidelines4/5

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

The description provides clear context for usage by specifying it returns 'comprehensive information about the constellation composition server,' implying it should be used for server-level queries. However, it does not explicitly state when not to use it or name alternatives, such as using sibling tools for constellation-specific data instead.

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/dmarsters/constellation-composition-mcp'

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