Skip to main content
Glama
tembo-io

Tembo MCP Server

Official
by tembo-io

get_all_apps

Retrieve detailed attributes for all applications on the Tembo Cloud platform, enabling streamlined management and oversight of resources via the Tembo MCP Server.

Instructions

Get attributes for all apps

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_all_apps' tool. It calls temboClient.getAllApps() and returns the response as a JSON string in the tool result format.
    get_all_apps: async () => {
    	const response = await temboClient.getAllApps();
    	return {
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify(response.data ?? response.error, null, 2),
    			},
    		],
    	};
    },
  • The schema definition for the 'get_all_apps' tool, including name, description, and empty input schema (no parameters required).
    {
    	name: "get_all_apps" as const,
    	description: "Get attributes for all apps",
    	inputSchema: {
    		type: "object",
    		properties: {},
    	},
    },
  • src/index.ts:32-34 (registration)
    Registration of the ListTools handler, which returns the TOOLS array including the schema for 'get_all_apps'.
    server.setRequestHandler(ListToolsRequestSchema, () => {
    	return { tools: TOOLS };
    });
  • src/index.ts:36-59 (registration)
    Registration of the CallTool handler, which dispatches to TOOL_HANDLERS[toolName] if allowed, thus invoking the 'get_all_apps' handler when requested.
    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. It states 'Get attributes for all apps', which implies a read-only operation, but doesn't disclose behavioral traits such as permissions needed, rate limits, pagination, or what happens if no apps exist. The description is minimal and lacks critical operational context.

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: 'Get attributes for all apps'. It's front-loaded with the core action and resource, with zero wasted words. It appropriately sized for a simple, parameterless tool.

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's simplicity (0 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what 'attributes' include, the return format, or any behavioral aspects like error handling or data freshness. For a tool that retrieves all apps, more context on output and usage is needed to be fully helpful.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so it meets the baseline for a parameterless tool. No additional value is required beyond stating the purpose.

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 'Get attributes for all apps' clearly states the verb ('Get') and resource ('all apps'), but it's somewhat vague about what 'attributes' specifically means. It distinguishes from siblings like 'get_app' (singular) and 'get_all_instances' (different resource), but lacks specificity about the scope or nature of the attributes.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_app' (for a single app) or 'get_all_instances' (for instances). The description implies it's for retrieving all apps, but doesn't specify prerequisites, constraints, or comparative use cases with sibling tools.

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