Skip to main content
Glama
tembo-io

Tembo MCP Server

Official
by tembo-io

get_app

Retrieve detailed attributes of a specific app type by specifying its category, enabling streamlined management of Tembo Cloud resources through the MCP server.

Instructions

Get the attributes of a single App

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesThe app type to get details for

Implementation Reference

  • The asynchronous handler function for the 'get_app' tool. It extracts the 'type' parameter from the request, calls temboClient.getApp with it, and returns the response data or error as JSON-formatted text content.
    get_app: async (request) => {
    	const { type } = request.params.arguments as { type: string };
    	const response = await temboClient.getApp({ path: { type } });
    	return {
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify(response.data ?? response.error, null, 2),
    			},
    		],
    	};
    },
  • The tool registration object defining the name, description, and input schema for 'get_app', which requires a 'type' string parameter.
    {
    	name: "get_app" as const,
    	description: "Get the attributes of a single App",
    	inputSchema: {
    		type: "object",
    		properties: {
    			type: {
    				type: "string",
    				description: "The app type to get details for",
    			},
    		},
    		required: ["type"],
    	},
    },
  • src/index.ts:32-34 (registration)
    Registers the list tools handler, which returns the TOOLS array including the 'get_app' tool definition.
    server.setRequestHandler(ListToolsRequestSchema, () => {
    	return { tools: TOOLS };
    });
  • src/index.ts:36-59 (registration)
    Registers the call tool handler, which dispatches to the specific TOOL_HANDLERS[toolName] including 'get_app' if allowed.
    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 full burden for behavioral disclosure. It states this is a read operation ('Get'), but doesn't describe what 'attributes' are returned, whether there are permissions required, rate limits, error conditions, or how the tool behaves when the app doesn't exist. For a tool with zero annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single, efficient sentence that directly states the tool's purpose. It's appropriately sized for a simple tool with one parameter, though it could be slightly more informative without sacrificing conciseness.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'attributes' are returned, the format of the response, or any behavioral aspects. For a tool that presumably returns structured data about an app, more context is needed to be complete.

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 schema description coverage is 100%, so the schema already documents the single parameter 'type' as 'The app type to get details for'. The description adds no additional parameter semantics beyond what the schema provides, maintaining the baseline score of 3.

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 ('attributes of a single App'), making the purpose understandable. It distinguishes this from sibling tools like 'get_all_apps' by specifying 'single App', but doesn't explicitly contrast with other similar tools like 'get_instance' or 'get_instance_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. It doesn't mention when this tool is appropriate compared to 'get_all_apps' for multiple apps, or 'get_instance' for instance details, nor does it specify any prerequisites or context 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