Skip to main content
Glama

spix_playbook_create

Create call or SMS playbooks for AI agents with voice, persona, and automation settings to manage phone communications.

Instructions

Create a new call or SMS playbook

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesPlaybook type
nameYesPlaybook name
goalNoCall playbook goal
personaNoAI persona description
briefingNoPlaybook briefing text
contextNoPlaybook context
voice_idNoVoice UUID for TTS
languageNoLanguage code (e.g. en, es, fr)
default_emotionNoDefault TTS emotion
speaking_rateNoSpeaking rate (0.6-1.5)
tts_volumeNoTTS volume (0.5-2.0)
max_duration_secNoMax call duration in seconds
recordNoRecord calls
amd_actionNoAnswering machine detection action

Implementation Reference

  • The create_tool_handler function is the general handler for all MCP tools, including 'spix_playbook_create'. It resolves the tool name to a schema, validates session/access, builds the endpoint URL, dispatches the request using the session client, and formats the response.
    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 CommandSchema definition for 'playbook.create', which is the underlying command for the MCP tool 'spix_playbook_create'. It defines the HTTP method (POST), endpoint (/playbooks), and required parameters.
    CommandSchema(
        path="playbook.create",
        cli_usage="spix playbook create --type <call|sms> --name <n>",
        http_method="POST",
        api_endpoint="/playbooks",
        mcp_expose="tool",
        mcp_profile="safe",
        description="Create a new call or SMS playbook",
        params=[
            CommandParam("type", "enum", required=True, choices=["call", "sms"], description="Playbook type"),
            CommandParam("name", "string", required=True, description="Playbook name"),
            CommandParam("goal", "string", description="Call playbook goal"),
            CommandParam("persona", "string", description="AI persona description"),
            CommandParam("briefing", "string", description="Playbook briefing text"),
            CommandParam("context", "string", description="Playbook context"),
            CommandParam("voice_id", "uuid", description="Voice UUID for TTS"),
            CommandParam("language", "string", description="Language code (e.g. en, es, fr)"),
            CommandParam("default_emotion", "string", description="Default TTS emotion"),
            CommandParam("speaking_rate", "number", description="Speaking rate (0.6-1.5)"),
            CommandParam("tts_volume", "number", description="TTS volume (0.5-2.0)"),
            CommandParam("max_duration_sec", "integer", description="Max call duration in seconds"),
            CommandParam("record", "boolean", default=True, description="Record calls"),
            CommandParam(
                "amd_action",
                "enum",
                choices=["hang_up", "voicemail_leave_message", "retry_later"],
                description="Answering machine detection action",
            ),
        ],
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It states this creates something but doesn't mention permission requirements, whether this is a write operation, what happens on success/failure, or any rate limits. The description doesn't contradict annotations (since none exist), but provides inadequate behavioral context for a creation tool.

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 a single, efficient sentence that states exactly what the tool does without any wasted words. It's perfectly front-loaded and contains no unnecessary information, making it easy for an agent to parse quickly.

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?

For a creation tool with 14 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what a playbook is, what happens after creation, whether there are constraints or dependencies, or what the expected return looks like. The agent would need to guess about many important operational aspects.

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?

With 100% schema description coverage, the baseline score is 3. The description adds no additional parameter information beyond what's already documented in the schema. It doesn't explain relationships between parameters (like how 'type' affects which other parameters are relevant) or provide usage examples, but the schema already documents all 14 parameters thoroughly.

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 action ('Create') and resource ('call or SMS playbook'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'spix_playbook_clone' or 'spix_playbook_update' that also involve playbook creation/modification, preventing a perfect score.

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 about when to use this tool versus alternatives like 'spix_playbook_clone' or 'spix_playbook_update'. There's no mention of prerequisites, appropriate contexts, or limitations that would help an agent decide when this is the right tool to invoke.

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