Skip to main content
Glama
appwrite

Appwrite MCP Server

Official
by appwrite

tables_db_delete_transaction

Remove a database transaction by its unique ID in Appwrite to manage data integrity and clean up records.

Instructions

Delete a transaction by its unique ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transaction_idYesTransaction ID.

Implementation Reference

  • Registers the TablesDB Appwrite service with the tool manager under the name 'tables_db'. This enables dynamic tool creation for all public methods on TablesDB, prefixed with 'tables_db_', such as 'tables_db_delete_transaction' if TablesDB has a 'delete_transaction' method.
    if args.tables_db:
        tools_manager.register_service(Service(TablesDB(client), "tables_db"))
    if args.users:
  • Dynamically generates tool registrations for all public methods of the service. Constructs tool name as '{service_name}_{method_name}' (e.g., 'tables_db_delete_transaction'), creates input schema from type hints and docstrings, and stores the tool definition along with the bound method as the handler.
    def list_tools(self) -> Dict[str, Dict]:
        """Lists all available tools for this service"""
        tools = {}
    
        for name, func in inspect.getmembers(self.service, predicate=inspect.ismethod):
            if name.startswith('_'): # Skip private methods
                continue
    
            original_func = func.__func__
            
            # Skip if not from the service's module
            if original_func.__module__ != self.service.__class__.__module__:
                continue
    
            # Get the overridden name if it exists
            tool_name = self._method_name_overrides.get(name, f"{self.service_name}_{name}")
    
            docstring = parse(original_func.__doc__)
            signature = inspect.signature(original_func)
            type_hints = get_type_hints(original_func)
    
            properties = {}
            required = []
    
            for param_name, param in signature.parameters.items():
                if param_name == 'self':
                    continue
    
                param_type = type_hints.get(param_name, str)
                properties[param_name] = self.python_type_to_json_schema(param_type)
                properties[param_name]["description"] = f"Parameter '{param_name}'"
                
                for doc_param in docstring.params:
                    if doc_param.arg_name == param_name:
                        properties[param_name]["description"] = doc_param.description
    
                if param.default is param.empty:
                    required.append(param_name)
    
            tool_definition = Tool(
                name=tool_name,
                description=f"{docstring.short_description or "No description available"}",
                inputSchema={
                    "type": "object",
                    "properties": properties,
                    "required": required
                }
            )
            
            tools[tool_name] = {
                "definition": tool_definition,
                "function": func
            }
            
        return tools
  • Generates JSON schema for tool parameters from Python type hints, supporting basic types, Optionals, Lists, Dicts, used in tool inputSchema.
    def python_type_to_json_schema(self, py_type: Any) -> dict:
        """Converts Python type hints to JSON Schema types."""
        type_mapping = {
            str: "string",
            int: "integer",
            float: "number",
            bool: "boolean",
            list: "array",
            dict: "object"
        }
        
        # Handle basic types
        if py_type in type_mapping:
            return {"type": type_mapping[py_type]}
        
        # Handle Optional types (Union[type, None])
        if hasattr(py_type, "__origin__") and py_type.__origin__ is Union:
            args = getattr(py_type, "__args__", ())
            if len(args) == 2 and args[1] is type(None):
                schema = self.python_type_to_json_schema(args[0])
                return schema
        
        # Handle List, Dict, and other generic types
        if hasattr(py_type, "__origin__"):
            origin = py_type.__origin__
            args = getattr(py_type, "__args__", ())
            
            # Handle List[T]
            if origin is list or origin is List:
                if args:
                    item_schema = self.python_type_to_json_schema(args[0])
                    return {
                        "type": "array",
                        "items": item_schema
                    }
                return {"type": "array"}
            
            # Handle Dict[K, V]
            if origin is dict or origin is Dict:
                if len(args) >= 2:
                    value_schema = self.python_type_to_json_schema(args[1])
                    return {
                        "type": "object",
                        "additionalProperties": value_schema
                    }
                return {"type": "object"}
        
        # Default to string for unknown types
        return {"type": "string"}
  • Executes the tool by retrieving the registered tool info, invoking the bound service method (e.g., TablesDB.delete_transaction) with arguments, and formatting the result as TextContent, handling Appwrite and general exceptions.
    @server.call_tool()
    async def handle_call_tool(
        name: str, arguments: dict | None
    ) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
        
        try:
            tool_info = tools_manager.get_tool(name)
            if not tool_info:
                raise McpError(f"Tool {name} not found")
            
            bound_method = tool_info["function"]
            result = bound_method(**(arguments or {}))
            if hasattr(result, 'to_dict'):
                result_dict = result.to_dict()
                return [types.TextContent(type="text", text=str(result_dict))]
            return [types.TextContent(type="text", text=str(result))]
        except AppwriteException as e:
            return [types.TextContent(type="text", text=f"Appwrite Error: {str(e)}")]
        except Exception as e:
            return [types.TextContent(type="text", text=f"Error: {str(e)}")]
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. While 'Delete' implies a destructive mutation, the description doesn't address critical behavioral aspects: whether deletion is permanent or reversible, what permissions are required, whether related data is affected, or what happens if the transaction doesn't exist. For a destructive operation with zero annotation coverage, this is inadequate.

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 maximally concise - a single sentence that states exactly what the tool does with zero wasted words. It's front-loaded with the core action and doesn't bury important information in unnecessary verbiage.

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 destructive deletion tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address the mutation's consequences, error conditions, or return values. Given the complexity of database operations and the complete lack of structured behavioral information, the description should provide more context about what 'delete' actually means in this system.

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 description coverage is 100%, so the schema already documents the single 'transaction_id' parameter. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain what constitutes a valid transaction ID, where to find it, or format requirements. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Delete') and target resource ('a transaction by its unique ID'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'tables_db_delete', 'tables_db_delete_row', or 'tables_db_delete_rows', which all perform deletion operations on different database entities.

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. With multiple deletion tools available (delete, delete_row, delete_rows, delete_table, delete_column, delete_index), the agent receives no help distinguishing this transaction-specific deletion from other deletion operations.

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/appwrite/mcp-for-api'

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