Skip to main content
Glama
tembo-io

Tembo MCP Server

Official
by tembo-io

patch_instance

Modify attributes of a Tembo Cloud instance, including CPU, memory, storage, environment, and replicas, using organization and instance IDs.

Instructions

Update attributes on an existing Tembo instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpuNo
environmentNo
instance_idYes
instance_nameNo
memoryNo
org_idYesOrganization ID that owns the instance
replicasNo
spotNo
storageNo

Implementation Reference

  • The asynchronous handler function that implements the core logic of the 'patch_instance' tool. It destructures the request arguments typed as PatchInstance, calls temboClient.patchInstance with the path and body parameters, and returns the JSON-stringified response.
    patch_instance: async (request) => {
    	const { org_id, instance_id, ...props } = request.params
    		.arguments as PatchInstance & {
    		org_id: string;
    		instance_id: string;
    	};
    	const response = await temboClient.patchInstance({
    		body: { ...props },
    		path: { org_id, instance_id },
    	});
    	return {
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify(response.data ?? response.error, null, 2),
    			},
    		],
    	};
    },
  • src/tools.ts:178-230 (registration)
    The registration of the 'patch_instance' tool in the TOOLS array, defining its name, description, and detailed inputSchema for MCP tool protocol.
    {
    	name: "patch_instance" as const,
    	description: "Update attributes on an existing Tembo instance",
    	inputSchema: {
    		type: "object",
    		properties: {
    			org_id: {
    				type: "string",
    				description: "Organization ID that owns the instance",
    			},
    			instance_id: { type: "string" },
    			instance_name: { type: "string" },
    			cpu: {
    				type: "string",
    				enum: ["0.25", "0.5", "1", "2", "4", "6", "8", "12", "16", "32"],
    			},
    			memory: {
    				type: "string",
    				enum: [
    					"512Mi",
    					"1Gi",
    					"2Gi",
    					"4Gi",
    					"8Gi",
    					"12Gi",
    					"16Gi",
    					"24Gi",
    					"32Gi",
    					"64Gi",
    				],
    			},
    			storage: {
    				type: "string",
    				enum: [
    					"10Gi",
    					"50Gi",
    					"100Gi",
    					"200Gi",
    					"300Gi",
    					"400Gi",
    					"500Gi",
    					"1Ti",
    					"1.5Ti",
    					"2Ti",
    				],
    			},
    			environment: { type: "string", enum: ["dev", "test", "prod"] },
    			replicas: { type: "integer" },
    			spot: { type: "boolean" },
    		},
    		required: ["org_id", "instance_id"],
    	},
    },
  • The input schema (JSON Schema) for the 'patch_instance' tool, defining properties like org_id, instance_id, resource specs, etc., with required fields.
    inputSchema: {
    	type: "object",
    	properties: {
    		org_id: {
    			type: "string",
    			description: "Organization ID that owns the instance",
    		},
    		instance_id: { type: "string" },
    		instance_name: { type: "string" },
    		cpu: {
    			type: "string",
    			enum: ["0.25", "0.5", "1", "2", "4", "6", "8", "12", "16", "32"],
    		},
    		memory: {
    			type: "string",
    			enum: [
    				"512Mi",
    				"1Gi",
    				"2Gi",
    				"4Gi",
    				"8Gi",
    				"12Gi",
    				"16Gi",
    				"24Gi",
    				"32Gi",
    				"64Gi",
    			],
    		},
    		storage: {
    			type: "string",
    			enum: [
    				"10Gi",
    				"50Gi",
    				"100Gi",
    				"200Gi",
    				"300Gi",
    				"400Gi",
    				"500Gi",
    				"1Ti",
    				"1.5Ti",
    				"2Ti",
    			],
    		},
    		environment: { type: "string", enum: ["dev", "test", "prod"] },
    		replicas: { type: "integer" },
    		spot: { type: "boolean" },
    	},
    	required: ["org_id", "instance_id"],
    },
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 'Update' implies a mutation operation, it doesn't describe what happens during the update (e.g., whether the instance restarts, if changes are immediate, permission requirements, or potential downtime). This leaves significant gaps in understanding 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.

Conciseness5/5

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

The description is a single, efficient sentence that gets straight to the point with no wasted words. It's appropriately front-loaded with the core action and resource, making it easy 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 mutation tool with 9 parameters, low schema coverage (11%), no annotations, and no output schema, the description is inadequate. It doesn't explain the update process, parameter meanings, expected outcomes, or error conditions, leaving too much undefined for reliable agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 11% (only org_id has a description), so the description must compensate but fails to do so. It mentions 'attributes' generally but doesn't explain what the 9 parameters represent, their relationships, or which are optional versus required beyond what the schema minimally indicates.

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 ('Update attributes') and target resource ('existing Tembo instance'), which distinguishes it from sibling tools like create_instance and delete_instance. However, it doesn't specify which attributes can be updated or the scope of changes, making it slightly less specific than ideal.

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 create_instance or restore_instance. There's no mention of prerequisites, constraints, or typical use cases, leaving the agent to infer usage from the tool name alone.

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