Skip to main content
Glama
tembo-io

Tembo MCP Server

Official
by tembo-io

delete_instance

Remove a specific Tembo Cloud instance by providing the organization ID and instance ID to manage resources effectively.

Instructions

Delete an existing Tembo instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYesDelete this instance id
org_idYesOrganization id of the instance to delete

Implementation Reference

  • The handler function for the 'delete_instance' tool. It extracts org_id and instance_id from the request arguments, calls temboClient.deleteInstance with the path parameters, and returns the JSON-stringified response or error.
    delete_instance: async (request) => {
    	const { org_id, instance_id } = request.params.arguments as {
    		org_id: string;
    		instance_id: string;
    	};
    	const response = await temboClient.deleteInstance({
    		path: { org_id, instance_id },
    	});
    	return {
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify(response.data ?? response.error, null, 2),
    			},
    		],
    	};
    },
  • The tool schema definition for 'delete_instance', including name, description, and inputSchema specifying required org_id and instance_id.
    {
    	name: "delete_instance" as const,
    	description: "Delete an existing Tembo instance",
    	inputSchema: {
    		type: "object",
    		properties: {
    			org_id: {
    				type: "string",
    				description: "Organization id of the instance to delete",
    			},
    			instance_id: { type: "string", description: "Delete this instance id" },
    		},
    		required: ["org_id", "instance_id"],
    	},
    },
  • src/index.ts:32-34 (registration)
    Registration of all tools (including delete_instance schema via TOOLS) for the ListToolsRequestHandler.
    server.setRequestHandler(ListToolsRequestSchema, () => {
    	return { tools: TOOLS };
    });
  • src/index.ts:36-59 (registration)
    Dynamic registration of tool handlers (including delete_instance via TOOL_HANDLERS) for the CallToolRequestHandler.
    server.setRequestHandler(
    	CallToolRequestSchema,
    	async (request): Promise<z.infer<typeof CallToolResultSchema>> => {
    		const toolName = request.params.name;
    
    		try {
    			if (isAllowedTool(toolName)) {
    				return await TOOL_HANDLERS[toolName](request);
    			}
    
    			throw new Error(`Unknown tool: ${toolName}`);
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: "text",
    						text: `Error: ${error instanceof Error ? error.message : String(error)}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	},
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes an instance, implying a destructive, irreversible action, but lacks details on permissions required, confirmation steps, effects on associated resources, or error handling. This is a significant gap for a mutation 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, direct sentence with zero wasted words, front-loading the key action and resource. It is appropriately sized for a simple tool with well-documented parameters.

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 tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as the consequences of deletion, required permissions, or what the tool returns upon success or failure, leaving significant gaps for an AI agent to understand the tool's behavior fully.

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, clearly documenting both parameters ('instance_id' and 'org_id') with their purposes. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 the resource ('an existing Tembo instance'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'patch_instance' or 'restore_instance', but the verb 'Delete' is specific enough to convey the core function.

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 like 'patch_instance' or 'restore_instance', nor does it mention prerequisites or conditions for deletion. It simply states what the tool does without contextual usage information.

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

Related 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/tembo-io/mcp-server-tembo'

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