Skip to main content
Glama
dmarsters

Constellation Composition MCP Server

by dmarsters

List All Available Constellations

list_all_constellations
Read-onlyIdempotent

Retrieve all 22 major constellations with abbreviations and themes to browse compositional patterns for AI image generation.

Instructions

List all available constellations with basic information.

Provides a quick overview of all 22 major constellations available in the system, including their abbreviations and primary themes. Useful for browsing options or understanding the full scope of available compositional patterns.

Args: response_format: Output format ('markdown' or 'json')

Returns: str: Complete list of constellations with basic metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNoOutput format for responses.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the 'list_all_constellations' MCP tool which lists all available constellations with their basic metadata.
    @mcp.tool(
        name="list_all_constellations",
        annotations={
            "title": "List All Available Constellations",
            "readOnlyHint": True,
            "destructiveHint": False,
            "idempotentHint": True,
            "openWorldHint": False
        }
    )
    async def list_all_constellations(response_format: ResponseFormat = ResponseFormat.MARKDOWN) -> str:
        """
        List all available constellations with basic information.
        
        Provides a quick overview of all 22 major constellations available in the system,
        including their abbreviations and primary themes. Useful for browsing options
        or understanding the full scope of available compositional patterns.
        
        Args:
            response_format: Output format ('markdown' or 'json')
        
        Returns:
            str: Complete list of constellations with basic metadata
        """
        
        constellation_list = []
        for name, data in sorted(CONSTELLATIONS.items()):
            constellation_list.append({
                'name': name,
                'abbreviation': data.get('abbr'),
                'theme': data.get('theme'),
                'shape': data.get('shape')
            })
        
        if response_format == ResponseFormat.JSON:
            return json.dumps({
                'constellations': constellation_list,
                'total_count': len(constellation_list)
            }, indent=2)
        else:
            md = f"# Available Constellations ({len(constellation_list)})\n\n"
            for item in constellation_list:
                md += f"## {item['name']} ({item['abbreviation']})\n\n"
                md += f"**Theme:** {item['theme']}\n\n"
                md += f"**Shape Pattern:** {item['shape'].replace('_', ' ').title()}\n\n"
                md += "---\n\n"
            return md
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds valuable context beyond this: it specifies the exact count (22 constellations), the type of information returned (abbreviations, primary themes), and characterizes it as a 'quick overview' for 'browsing options'. This enhances understanding 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose statement, usage context, and separate Args/Returns sections. It is appropriately sized, but the Args section repeats schema information without adding value, slightly reducing efficiency. Most sentences earn their place by providing useful context.

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 low complexity (1 optional parameter), rich annotations (safety and behavior hints), and existence of an output schema (implied by 'Returns' note), the description is complete. It covers purpose, usage context, and output content adequately without needing to detail return values or behavioral traits already in annotations.

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%, with the parameter 'response_format' fully documented in the schema (enum values, default). The description repeats this information in the Args section but adds no additional semantic meaning beyond what the schema provides, such as guidance on when to choose one format over another. Baseline 3 is appropriate given high schema coverage.

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 verb ('List') and resource ('all available constellations'), specifying the scope as 'all 22 major constellations' with 'basic information including abbreviations and primary themes'. It distinguishes from siblings like 'search_constellations' (filtered search) and 'list_constellation_presets' (presets rather than 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 ('useful for browsing options or understanding the full scope'), but does not explicitly state when not to use it or name specific alternatives. It implies this is for a complete overview vs. filtered searches, but lacks explicit exclusions or named sibling tool comparisons.

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