Skip to main content
Glama
tembo-io

Tembo MCP Server

Official
by tembo-io

get_all_instances

Retrieve all Tembo instances within an organization by providing the org_id, enabling efficient management of cloud resources through the Tembo MCP Server.

Instructions

Get all Tembo instances in an organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
org_idYesOrganization id for the request

Implementation Reference

  • Handler function that implements the 'get_all_instances' tool logic by fetching all instances for the given organization ID using temboClient.getAll and returning the result as text content.
    get_all_instances: async (request) => {
    	const { org_id } = request.params.arguments as { org_id: string };
    	const response = await temboClient.getAll({ path: { org_id } });
    	return {
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify(response.data ?? response.error, null, 2),
    			},
    		],
    	};
    },
  • Input schema definition for the 'get_all_instances' tool, part of the TOOLS array, specifying the required 'org_id' parameter.
    {
    	name: "get_all_instances" as const,
    	description: "Get all Tembo instances in an organization",
    	inputSchema: {
    		type: "object",
    		properties: {
    			org_id: {
    				type: "string",
    				description: "Organization id for the request",
    			},
    		},
    		required: ["org_id"],
    	},
    },
  • src/index.ts:32-34 (registration)
    Registration of tool list handler, which returns the TOOLS array containing the schema for 'get_all_instances'.
    server.setRequestHandler(ListToolsRequestSchema, () => {
    	return { tools: TOOLS };
    });
  • src/index.ts:36-59 (registration)
    Registration of the generic tool call handler that dispatches to TOOL_HANDLERS[toolName], enabling execution of 'get_all_instances'.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but does not describe traits like whether this is a read-only operation, potential rate limits, authentication needs, or what the return format looks like (e.g., list structure, pagination). This leaves significant gaps for an agent.

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 no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose 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 lack of annotations and output schema, the description is incomplete. It does not address behavioral aspects like safety, performance, or return values, which are crucial for an agent to use this tool effectively in context with its siblings.

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, with 'org_id' documented as 'Organization id for the request'. The description does not add any additional meaning beyond this, such as format examples or constraints, but the schema provides adequate baseline information.

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 ('all Tembo instances in an organization'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'get_instance' or 'get_all_apps', which would be needed for a perfect score.

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 such as 'get_instance' (for a single instance) or 'get_all_apps' (for apps instead of instances). There is no mention of prerequisites, exclusions, or specific contexts for usage.

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