Skip to main content
Glama

spix_playbook_show

Display detailed information about a playbook by providing its unique ID, including configuration, steps, and parameters.

Instructions

Show playbook details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playbook_idYesPlaybook ID

Implementation Reference

  • The CommandSchema definition for the 'playbook.show' tool. It defines the MCP tool name 'spix_playbook_show', the API endpoint '/playbooks/{playbook_id}', HTTP method GET, and requires a 'playbook_id' positional argument. This is the schema that defines the tool.
    CommandSchema(
        path="playbook.show",
        cli_usage="spix playbook show <playbook_id>",
        http_method="GET",
        api_endpoint="/playbooks/{playbook_id}",
        mcp_expose="tool",
        mcp_profile="safe",
        description="Show playbook details",
        positional_args=[
            CommandParam("playbook_id", "string", required=True, description="Playbook ID"),
        ],
    ),
  • Registration of MCP tools. At line 90, the tool name is constructed as 'spix_playbook_show' from the schema path 'playbook.show'. Tools are registered with the MCP server via list_tools() and dispatched via call_tool() which delegates to create_tool_handler.
    # ─── Tool Surface ─────────────────────────────────────────────────────────
    tool_schemas = get_mcp_tools(profile=tool_profile, disabled=disabled_tools)
    tool_defs: list[Tool] = []
    
    for schema in tool_schemas:
        # Convert path to tool name: playbook.create -> spix_playbook_create
        tool_name = f"spix_{schema.path.replace('.', '_')}"
        tool_defs.append(
            Tool(
                name=tool_name,
                description=schema.description or f"Spix {schema.path}",
                inputSchema=build_json_schema(schema),
            )
        )
    
    @server.list_tools()
    async def list_tools() -> list[Tool]:
        return tool_defs
    
    @server.call_tool()
    async def call_tool(name: str, arguments: dict) -> Sequence[TextContent]:
        result = await create_tool_handler(session, name, arguments)
        return result
  • The generic tool handler (create_tool_handler) that processes all tool calls including 'spix_playbook_show'. It uses get_schema_by_tool_name() to look up the playbook.show schema, then builds the endpoint URL '/playbooks/{playbook_id}' by substituting the playbook_id path parameter, and executes a GET request via the API client.
    async def create_tool_handler(
        session: McpSessionContext,
        tool_name: str,
        arguments: dict,
    ) -> list:
        """Execute an MCP tool call by dispatching to the backend API.
    
        This function:
        1. Resolves the tool name to a command schema
        2. Validates session scope (playbook access, channel access)
        3. Builds the API request
        4. Dispatches to the backend
        5. Returns the response as MCP TextContent
    
        Args:
            session: The MCP session context for scope validation.
            tool_name: The MCP tool name (e.g., "spix_playbook_create").
            arguments: The tool arguments from the MCP client.
    
        Returns:
            List containing a single TextContent with the JSON response.
        """
        # Import here to avoid circular imports and handle missing mcp package
        try:
            from mcp.types import TextContent
        except ImportError:
            # Fallback for when mcp is not installed
            class TextContent:  # type: ignore[no-redef]
                def __init__(self, type: str, text: str) -> None:
                    self.type = type
                    self.text = text
    
        # Resolve tool name to schema
        schema = get_schema_by_tool_name(tool_name)
        if not schema:
            return [
                TextContent(
                    type="text",
                    text=orjson.dumps(
                        {"ok": False, "error": {"code": "unknown_tool", "message": f"Unknown tool: {tool_name}"}}
                    ).decode(),
                )
            ]
    
        # Validate tool access (not disabled)
        try:
            session.validate_tool_access(schema.path)
        except Exception as e:
            from spix_mcp.session import McpScopeError
    
            if isinstance(e, McpScopeError):
                return [TextContent(type="text", text=orjson.dumps({"ok": False, "error": e.to_dict()}).decode())]
            raise
    
        # Validate channel access if applicable
        channel = infer_channel_from_tool(schema.path)
        if channel:
            try:
                session.validate_channel_access(channel)
            except Exception as e:
                from spix_mcp.session import McpScopeError
    
                if isinstance(e, McpScopeError):
                    return [TextContent(type="text", text=orjson.dumps({"ok": False, "error": e.to_dict()}).decode())]
                raise
    
        # Handle playbook_id: validate and apply default
        playbook_id = arguments.get("playbook_id")
        try:
            effective_playbook = session.validate_playbook_access(playbook_id)
            if effective_playbook and not playbook_id:
                # Apply default playbook
                arguments["playbook_id"] = effective_playbook
        except Exception as e:
            from spix_mcp.session import McpScopeError
    
            if isinstance(e, McpScopeError):
                return [TextContent(type="text", text=orjson.dumps({"ok": False, "error": e.to_dict()}).decode())]
            raise
    
        # Build endpoint URL with path parameters
        endpoint, remaining_args = build_endpoint_url(schema, arguments)
    
        # Dispatch to backend API
        client = session.client
        method = schema.http_method.lower()
    
        if method == "get":
            response = await asyncio.to_thread(client.get, endpoint, params=remaining_args if remaining_args else None)
        elif method == "post":
            response = await asyncio.to_thread(client.post, endpoint, json=remaining_args if remaining_args else None)
        elif method == "patch":
            response = await asyncio.to_thread(client.patch, endpoint, json=remaining_args if remaining_args else None)
        elif method == "delete":
            response = await asyncio.to_thread(client.delete, endpoint, params=remaining_args if remaining_args else None)
        else:
            response = await asyncio.to_thread(client.get, endpoint)
    
        # Build response envelope
        envelope: dict = {"ok": response.ok, "meta": response.meta}
        if response.ok:
            envelope["data"] = response.data
            if response.pagination:
                envelope["pagination"] = response.pagination
            if response.warnings:
                envelope["warnings"] = response.warnings
        else:
            envelope["error"] = response.error
    
        return [TextContent(type="text", text=orjson.dumps(envelope).decode())]
  • The get_schema_by_tool_name() function in tools.py (lines 23-50) resolves the MCP tool name 'spix_playbook_show' back to the 'playbook.show' CommandSchema by converting underscores to dots and matching against the registry.
        required: bool = False
        description: str = ""
        choices: list[str] = field(default_factory=list)
        default: object = None
    
    
    @dataclass
    class CommandSchema:
        """Schema for a CLI command.
    
        Each command maps to:
        - A Click command in the CLI
        - Optionally an MCP tool or resource
        """
    
        path: str  # e.g., "playbook.create", "call.show"
        cli_usage: str  # e.g., "spix playbook create"
        http_method: str  # "GET", "POST", "PATCH", "DELETE"
        api_endpoint: str  # e.g., "/playbooks", "/calls/{id}"
        params: list[CommandParam] = field(default_factory=list)
        positional_args: list[CommandParam] = field(default_factory=list)
        mcp_expose: Literal["tool", "resource", None] = None
        mcp_profile: Literal["safe", "full"] = "safe"  # "safe" = included in both profiles
        destructive: bool = False
        financial: bool = False
        description: str = ""
Behavior2/5

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

With no annotations, the description carries the full transparency burden. It only states 'Show playbook details' without mentioning read-only nature, error behavior, or any side effects. Limited behavioral insight.

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?

A single, clear sentence that is appropriately front-loaded. While minimal, it efficiently conveys the core purpose without extraneous content.

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

Completeness2/5

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

Given the lack of output schema and annotations, the description fails to specify what 'details' are returned (e.g., name, rules, status). The provided information is insufficient for the agent to fully understand the tool's output or behavior.

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 coverage is 100% with a description for playbook_id. The description adds no further meaning beyond what the schema provides, so the baseline of 3 applies.

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 'Show playbook details' clearly identifies the verb+resource and distinguishes this tool from siblings like spix_playbook_list or spix_playbook_create, indicating it retrieves details for a specific playbook.

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?

No guidance on when to use this tool vs alternatives (e.g., spix_playbook_list). No context on prerequisites or appropriate scenarios, leaving the agent without explicit usage direction.

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/Spix-HQ/spix-mcp'

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