Skip to main content
Glama
lmorchard

Oblique Strategies MCP Server

by lmorchard

list_editions

Browse available editions of the Oblique Strategies card deck to select creative prompts that help overcome creative blocks through lateral thinking.

Instructions

List all available editions and their descriptions.

Returns: Information about all available editions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual implementation of the 'list_editions' logic resides in the StrategiesManager class within strategies_core.py.
    def list_editions(self) -> Dict[str, Any]:
        """List all available editions and their descriptions."""
        edition_info = []
    
        for key, filename in self.EDITIONS.items():
            file_path = self.strategies_dir / filename
            if file_path.exists():
                try:
                    strategies = self.load_strategies(key)
                    count = len(strategies)
                except Exception:
                    count = 0
    
                edition_info.append(
                    {
                        "key": key,
                        "filename": filename,
                        "strategy_count": count,
                        "is_default": key == self.DEFAULT_EDITION,
                    }
                )
    
        return {"editions": edition_info, "default_edition": self.DEFAULT_EDITION}
  • The MCP tool registration and wrapper function for 'list_editions' in the MCP server setup.
    @mcp.tool()
    def list_editions() -> Dict[str, Any]:
        """
        List all available editions and their descriptions.
    
        Returns:
            Information about all available editions.
        """
        return manager.list_editions()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does and the return type, missing critical details like whether it's read-only, requires authentication, has rate limits, or pagination behavior. For a tool with no annotations, this is insufficient.

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 concise and front-loaded, with the main purpose stated first and a brief note on returns. It avoids unnecessary elaboration, though the 'Returns:' section could be slightly more informative. Overall, it's efficient with minimal waste.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, output schema exists), the description is adequate but lacks depth. It covers the basic purpose and return type, but without annotations, it misses behavioral context. The output schema helps, but the description could better explain what 'Information about all available editions' entails, such as format or scope.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The description correctly avoids unnecessary parameter information, earning a high score for not adding redundant content beyond the structured schema.

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

Purpose4/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: 'List all available editions and their descriptions.' It specifies the verb ('List') and resource ('editions'), making the action explicit. However, it doesn't differentiate from sibling tools like 'get_strategy' or 'search_strategies', which prevents a score of 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools or contexts where this tool is preferred, such as for browsing all editions versus searching or retrieving specific ones. This lack of comparative usage information limits its helpfulness.

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/lmorchard/oblique-strategies-mcp'

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