Skip to main content
Glama
dmarsters

Constellation Composition MCP Server

by dmarsters

List Phase 2.6 Rhythmic Presets

list_constellation_presets
Read-onlyIdempotent

Retrieve available rhythmic presets with parameters for temporal oscillation patterns between constellation states, enabling Phase 2.6 rhythmic composition and multi-domain limit cycle discovery.

Instructions

List all available Phase 2.6 rhythmic presets with their parameters.

Layer 1: Pure taxonomy lookup (0 tokens).

Returns preset names, periods, oscillation patterns, state pairs, and descriptions. Presets define temporal oscillation patterns between canonical constellation states for rhythmic composition and Tier 4D multi-domain limit cycle discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNoOutput format for responses.json

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool handler for 'list_constellation_presets', which lists rhythmic presets by reading from the 'CONSTELLATION_RHYTHMIC_PRESETS' dictionary.
        name="list_constellation_presets",
        annotations={
            "title": "List Phase 2.6 Rhythmic Presets",
            "readOnlyHint": True,
            "destructiveHint": False,
            "idempotentHint": True,
            "openWorldHint": False
        }
    )
    async def list_constellation_presets(
        response_format: ResponseFormat = ResponseFormat.JSON
    ) -> str:
        """
        List all available Phase 2.6 rhythmic presets with their parameters.
    
        Layer 1: Pure taxonomy lookup (0 tokens).
    
        Returns preset names, periods, oscillation patterns, state pairs,
        and descriptions. Presets define temporal oscillation patterns between
        canonical constellation states for rhythmic composition and Tier 4D
        multi-domain limit cycle discovery.
        """
        presets_info = {}
        for name, cfg in CONSTELLATION_RHYTHMIC_PRESETS.items():
            state_a = CONSTELLATION_CANONICAL_STATES[cfg["state_a"]]
            state_b = CONSTELLATION_CANONICAL_STATES[cfg["state_b"]]
            presets_info[name] = {
                "period": cfg["steps_per_cycle"],
                "pattern": cfg["pattern"],
                "num_cycles": cfg["num_cycles"],
                "total_steps": cfg["num_cycles"] * cfg["steps_per_cycle"],
                "state_a": {
                    "name": cfg["state_a"],
                    "constellation": state_a.get("source_constellation", ""),
                    "coordinates": {p: state_a[p] for p in CONSTELLATION_PARAMETER_NAMES}
                },
                "state_b": {
                    "name": cfg["state_b"],
                    "constellation": state_b.get("source_constellation", ""),
                    "coordinates": {p: state_b[p] for p in CONSTELLATION_PARAMETER_NAMES}
                },
                "description": cfg["description"]
            }
    
        if response_format == ResponseFormat.JSON:
            return json.dumps({
                "presets": presets_info,
                "all_periods": sorted(set(
                    p["steps_per_cycle"] for p in CONSTELLATION_RHYTHMIC_PRESETS.values()
                )),
                "parameter_names": CONSTELLATION_PARAMETER_NAMES,
                "count": len(presets_info)
            }, indent=2)
        else:
            md = "# Constellation Rhythmic Presets (Phase 2.6)\n\n"
            for name, info in presets_info.items():
                md += f"## {name}\n\n"
                md += f"**Period:** {info['period']} steps | "
                md += f"**Pattern:** {info['pattern']} | "
                md += f"**Total steps:** {info['total_steps']}\n\n"
                md += f"**Oscillates:** {info['state_a']['name']} "
                md += f"({info['state_a']['constellation']}) ↔ "
                md += f"{info['state_b']['name']} ({info['state_b']['constellation']})\n\n"
                md += f"*{info['description']}*\n\n---\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 annotations: it specifies this is a 'pure taxonomy lookup (0 tokens)' operation, describes what data is returned (preset names, periods, oscillation patterns, etc.), and explains the purpose of presets. No contradiction with annotations exists.

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 efficiently structured with two sentences: the first states the core purpose and return data, the second explains the broader context of presets. Every phrase adds value without redundancy. The 'Layer 1' note is concise and informative.

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 simplicity (one optional parameter, read-only operation), rich annotations, and existence of an output schema, the description is complete. It explains what the tool does, what data it returns, and the purpose of presets. The output schema will handle return value documentation, so the description appropriately focuses on context.

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 only one optional parameter (response_format) fully documented in the schema. The description doesn't mention parameters at all, which is acceptable given the high schema coverage. However, it doesn't add any semantic context about parameter usage beyond what the schema provides.

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 'Phase 2.6 rhythmic presets' with their parameters. It distinguishes from siblings like 'apply_constellation_preset' (which applies rather than lists) and 'list_all_constellations' (which lists constellations rather than presets). The mention of 'pure taxonomy lookup' further clarifies this is a retrieval operation.

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 when to use this tool: for 'taxonomy lookup' of presets with their parameters, and mentions their purpose for 'rhythmic composition and Tier 4D multi-domain limit cycle discovery.' However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings, though the context implies it's for listing rather than applying presets.

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