Skip to main content
Glama
tembo-io

Tembo MCP Server

Official
by tembo-io

get_instance

Retrieve a specific Tembo Cloud instance by providing the organization ID and instance ID, enabling users to manage Tembo resources efficiently.

Instructions

Get an existing Tembo instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYes
org_idYesOrganization ID that owns the instance

Implementation Reference

  • The async handler function for the 'get_instance' tool. Extracts org_id and instance_id from the request arguments, calls temboClient.getInstance, and returns the JSON-stringified response.
    get_instance: async (request) => {
    	const { org_id, instance_id } = request.params.arguments as {
    		org_id: string;
    		instance_id: string;
    	};
    	const response = await temboClient.getInstance({
    		path: { org_id, instance_id },
    	});
    	return {
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify(response.data ?? response.error, null, 2),
    			},
    		],
    	};
    },
  • src/tools.ts:148-162 (registration)
    The registration entry for the 'get_instance' tool in the TOOLS array, defining its name, description, and input schema.
    {
    	name: "get_instance" as const,
    	description: "Get an existing Tembo instance",
    	inputSchema: {
    		type: "object",
    		properties: {
    			org_id: {
    				type: "string",
    				description: "Organization ID that owns the instance",
    			},
    			instance_id: { type: "string" },
    		},
    		required: ["org_id", "instance_id"],
    	},
    },
  • The input schema for the 'get_instance' tool, defined inline in its registration, specifying required org_id and instance_id.
    {
    	name: "get_instance" as const,
    	description: "Get an existing Tembo instance",
    	inputSchema: {
    		type: "object",
    		properties: {
    			org_id: {
    				type: "string",
    				description: "Organization ID that owns the instance",
    			},
    			instance_id: { type: "string" },
    		},
    		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 the full burden of behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't clarify whether this requires authentication, has rate limits, returns partial or full instance data, or what happens if the instance doesn't exist. For a retrieval tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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, clear sentence with zero wasted words. It's appropriately front-loaded with the core purpose, making it easy for an agent to parse quickly without unnecessary elaboration.

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 tool has 2 required parameters, no annotations, no output schema, and moderate schema coverage (50%), the description is insufficiently complete. It doesn't address what data is returned, error conditions, or how this differs from sibling tools. For a retrieval operation in a system with multiple instance-related tools, more context is needed to guide proper usage.

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 50% (only 'org_id' has a description), and the description adds no parameter information beyond what's implied by the tool name. It doesn't explain what 'instance_id' represents or provide context about parameter relationships. Since schema coverage is moderate, the baseline is 3, but the description doesn't compensate for the undocumented 'instance_id' parameter.

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 verb ('Get') and resource ('an existing Tembo instance'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_all_instances' or 'get_instance_schema', which would require more specificity about what exactly is retrieved (metadata vs. full configuration vs. schema).

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 'get_all_instances' (for listing) or 'get_instance_schema' (for schema details). It also doesn't mention prerequisites or context for when this retrieval operation is appropriate, 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