Skip to main content
Glama

spix_phone_bind

Bind a phone number (E.164) to a playbook ID to integrate real phone numbers with automated call workflows.

Instructions

Bind phone number to playbook

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesPhone number (E.164)
playbook_idYesPlaybook ID to bind

Implementation Reference

  • The CommandSchema definition for 'phone.bind' - this is the schema that defines the 'spix_phone_bind' tool. It maps to POST /phone/numbers/{number}/bind, binds a phone number to a playbook, with positional arg 'number' and param 'playbook_id'.
    CommandSchema(
        path="phone.bind",
        cli_usage="spix phone bind <number> --playbook <id>",
        http_method="POST",
        api_endpoint="/phone/numbers/{number}/bind",
        mcp_expose="tool",
        mcp_profile="safe",
        description="Bind phone number to playbook",
        positional_args=[
            CommandParam("number", "string", required=True, description="Phone number (E.164)"),
        ],
        params=[
            CommandParam("playbook_id", "string", required=True, description="Playbook ID to bind"),
        ],
    ),
  • Tool registration in the MCP server. The path 'phone.bind' is converted to tool name 'spix_phone_bind' (line 90: tool_name = f"spix_{schema.path.replace('.', '_')}") and registered via the Tool schema.
    # ─── 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),
            )
        )
  • The generic tool handler (create_tool_handler) that dispatches all MCP tool calls including 'spix_phone_bind'. It resolves the tool name via get_schema_by_tool_name, validates session scope, builds the endpoint URL by substituting path params, and calls the backend API.
    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 that resolves 'spix_phone_bind' by stripping the 'spix_' prefix and matching 'phone_bind' → 'phone.bind' against the command registry.
    def get_schema_by_tool_name(tool_name: str) -> CommandSchema | None:
        """Look up a CommandSchema by MCP tool name.
    
        MCP tool names follow the pattern: spix_{path with dots replaced by underscores}
        e.g., "spix_playbook_create" -> "playbook.create"
    
        Args:
            tool_name: The MCP tool name (e.g., "spix_playbook_create").
    
        Returns:
            The matching CommandSchema, or None if not found.
        """
        # Remove the spix_ prefix
        if not tool_name.startswith("spix_"):
            return None
    
        path_part = tool_name[len("spix_") :]
    
        # Convert underscores back to dots for path lookup
        # We need to handle multi-part paths like "billing_credits_history" -> "billing.credits.history"
        # Try different dot positions to find the right one
        for cmd in COMMAND_REGISTRY:
            # Convert the command path to expected tool name format
            expected_tool = cmd.path.replace(".", "_")
            if expected_tool == path_part:
                return cmd
    
        return None
  • The build_endpoint_url function that substitutes the 'number' positional arg into the API endpoint '/phone/numbers/{number}/bind' for the spix_phone_bind tool call.
    def build_endpoint_url(schema: CommandSchema, arguments: dict) -> tuple[str, dict]:
        """Build the API endpoint URL with path parameters substituted.
    
        Args:
            schema: The command schema.
            arguments: The tool arguments.
    
        Returns:
            Tuple of (endpoint_url, remaining_arguments).
            Path parameters are removed from arguments and substituted into the URL.
        """
        endpoint = schema.api_endpoint
        remaining_args = dict(arguments)
    
        # Substitute path parameters
        for param in schema.positional_args:
            placeholder = f"{{{param.name}}}"
            if placeholder in endpoint and param.name in remaining_args:
                endpoint = endpoint.replace(placeholder, str(remaining_args.pop(param.name)))
    
        return endpoint, remaining_args
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It indicates a mutation (binding) but does not describe side effects, such as whether binding replaces an existing binding, if it requires specific permissions, or if it is reversible. The description is insufficient for an agent to understand the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single sentence with no fluff, but it is too terse. It lacks any structural elements (e.g., sections for usage notes) that would help an agent quickly parse important details. While concise, it sacrifices informativeness.

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 absence of annotations and output schema, the description should provide more context about the binding operation, such as whether it is idempotent, what the return value is, or how to unbind. The current description leaves significant gaps for a 2-parameter mutation tool.

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?

The input schema has 100% description coverage for its two required parameters. The description adds no additional meaning beyond 'phone number (E.164)' and 'Playbook ID to bind'. With high schema coverage, the description does not need to elaborate further, so a baseline of 3 is appropriate.

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 ('Bind') and the two resources ('phone number' and 'playbook'), making the tool's purpose straightforward. It distinguishes itself from siblings like spix_phone_unbind by being the opposite action. However, it could be more specific (e.g., 'Bind a phone number to a playbook for call routing').

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. For instance, it doesn't mention prerequisites (e.g., the phone number must already exist and not be bound) or whether binding multiple numbers to a playbook is allowed. This leaves the agent to infer usage from context.

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