Skip to main content
Glama

spix_billing_credits_history

Retrieve your credit usage history with an optional limit on results. Monitor and analyze spending patterns to track resource consumption.

Instructions

Show credit usage history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results

Implementation Reference

  • The CommandSchema registration for billing.credits.history. This defines the tool's path ('billing.credits.history'), HTTP method (GET), API endpoint ('/billing/credits/history'), and its single optional parameter 'limit'.
    CommandSchema(
        path="billing.credits.history",
        cli_usage="spix billing credits history",
        http_method="GET",
        api_endpoint="/billing/credits/history",
        mcp_expose="tool",
        mcp_profile="safe",
        description="Show credit usage history",
        params=[
            CommandParam("limit", "integer", default=50, description="Number of results"),
        ],
    ),
  • The tool is registered in the COMMAND_REGISTRY list with mcp_expose='tool', making it discoverable as an MCP tool named 'spix_billing_credits_history'.
        path="billing.credits.history",
        cli_usage="spix billing credits history",
        http_method="GET",
        api_endpoint="/billing/credits/history",
        mcp_expose="tool",
        mcp_profile="safe",
        description="Show credit usage history",
        params=[
            CommandParam("limit", "integer", default=50, description="Number of results"),
        ],
    ),
  • The get_schema_by_tool_name function resolves the MCP tool name 'spix_billing_credits_history' to its CommandSchema by removing the 'spix_' prefix and converting underscores back to dots for path lookup.
    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 generic create_tool_handler function that handles all tool executions including 'spix_billing_credits_history'. It looks up the schema, validates session scope, builds the endpoint URL ('/billing/credits/history'), dispatches a GET request via the SpixClient, and returns 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 server registration logic that converts schema path 'billing.credits.history' to the MCP tool name 'spix_billing_credits_history' using f"spix_{schema.path.replace('.', '_')}" and builds the Tool definition with inputSchema.
    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),
            )
        )
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'show' (read-only) but lacks details on ordering, default date range, pagination, or response structure. Does not disclose any behavioral traits beyond what is inferred from name.

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?

Extremely concise (4 words) and front-loaded. While efficient, it could be slightly more informative without losing conciseness.

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?

No output schema and no annotations. Description does not explain what 'credit usage history' includes (e.g., time range, granularity, fields). Incomplete for a tool with no other documentation.

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 one optional parameter 'limit' described as 'Number of results'. The description adds no extra meaning beyond the schema, so baseline score 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?

Description clearly states 'Show credit usage history' with a specific verb and resource. It is distinct from sibling tools like spix_billing_credits and spix_billing_status, but no explicit differentiation is provided.

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 versus alternatives (e.g., spix_billing_credits). No context about prerequisites or when not to use it.

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