Skip to main content
Glama
tembo-io

Tembo MCP Server

Official
by tembo-io

restore_instance

Restore a Tembo instance by specifying the organization ID, instance name, and recovery target time using the Tembo MCP Server to recover resources efficiently.

Instructions

Restore a Tembo instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_nameYes
org_idYesOrganization ID that owns the Tembo instance
restoreYes

Implementation Reference

  • The handler function for the 'restore_instance' tool. It extracts org_id and other properties from the request arguments, calls temboClient.restoreInstance with org_id in the path and props in the body, and returns the response as a text content block.
    restore_instance: async (request) => {
    	const { org_id, ...props } = request.params.arguments as RestoreInstance & {
    		org_id: string;
    	};
    	const response = await temboClient.restoreInstance({
    		body: { ...props },
    		path: { org_id },
    	});
    	return {
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify(response.data ?? response.error, null, 2),
    			},
    		],
    	};
    },
  • src/tools.ts:231-253 (registration)
    Registration of the 'restore_instance' tool in the TOOLS array, including name, description, and detailed inputSchema defining parameters like org_id, instance_name, and restore object with instance_id.
    {
    	name: "restore_instance" as const,
    	description: "Restore a Tembo instance",
    	inputSchema: {
    		type: "object",
    		properties: {
    			org_id: {
    				type: "string",
    				description: "Organization ID that owns the Tembo instance",
    			},
    			instance_name: { type: "string" },
    			restore: {
    				type: "object",
    				properties: {
    					instance_id: { type: "string" },
    					recovery_target_time: { type: "string", format: "date-time" },
    				},
    				required: ["instance_id"],
    			},
    		},
    		required: ["org_id", "instance_name", "restore"],
    	},
    },
  • Import of RestoreInstance type used for argument validation in the handler.
    RestoreInstance,
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 action ('restore') but doesn't explain what restoration entails (e.g., is it destructive to current data, does it require specific permissions, what are rate limits or side effects?). This lack of detail is a significant gap for a mutation tool with zero annotation coverage, though it doesn't contradict any annotations.

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 extremely concise with a single sentence, 'Restore a Tembo instance', which is front-loaded and wastes no words. While this brevity may under-specify the tool, it earns a high score for conciseness as every word directly contributes to the core purpose without redundancy.

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 complexity (3 parameters with nested objects, no annotations, no output schema, and low schema coverage), the description is incomplete. It doesn't address behavioral aspects, parameter meanings, or usage context, making it inadequate for an agent to reliably invoke this tool without additional inference or trial-and-error.

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 low at 33%, with only 'org_id' having a description. The tool description adds no parameter semantics beyond the name 'restore', failing to explain what 'instance_name', 'org_id', or the nested 'restore' object (with 'instance_id' and 'recovery_target_time') mean in context. This doesn't compensate for the schema's gaps, leaving most parameters poorly documented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Restore a Tembo instance' clearly states the verb ('restore') and resource ('Tembo instance'), making the basic purpose understandable. However, it doesn't specify what 'restore' means in this context (e.g., from backup, from deletion, to a previous state) or differentiate it from sibling tools like 'patch_instance' or 'create_instance', leaving some ambiguity about its specific 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. It doesn't mention prerequisites (e.g., needing a deleted or failed instance), exclusions (e.g., cannot restore while instance is running), or relationships to siblings like 'delete_instance' or 'get_instance', leaving the agent to infer usage context without explicit direction.

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