Skip to main content
Glama
tembo-io

Tembo MCP Server

Official
by tembo-io

ask_tembo

Query Tembo Docs to find answers and guidance on managing Tembo Cloud resources using natural language interactions.

Instructions

Ask a question to Tembo Docs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe ask query. For example, "how to create a Tembo instance"

Implementation Reference

  • The handler function for the 'ask_tembo' tool. It extracts the 'query' from the input arguments, calls temboClient.ask with the query, and returns the JSON-stringified response or error.
    ask_tembo: async (request) => {
    	const { query } = request.params.arguments as { query: string };
    	const response = await temboClient.ask({
    		query: {
    			query,
    		},
    	});
    	return {
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify(response.data ?? response.error, null, 2),
    			},
    		],
    	};
    },
  • The schema definition for the 'ask_tembo' tool, including name, description, and input schema requiring a 'query' string.
    {
    	name: "ask_tembo" as const,
    	description: "Ask a question to Tembo Docs",
    	inputSchema: {
    		type: "object",
    		properties: {
    			query: {
    				type: "string",
    				description:
    					'The ask query. For example, "how to create a Tembo instance"',
    			},
    		},
    		required: ["query"],
    	},
    },
  • src/index.ts:32-34 (registration)
    Registration of all tools (including 'ask_tembo') via the ListTools handler that returns the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, () => {
    	return { tools: TOOLS };
    });
  • src/index.ts:41-44 (registration)
    Dispatch logic in CallTool handler that routes to the specific TOOL_HANDLERS[toolName] for execution if allowed.
    try {
    	if (isAllowedTool(toolName)) {
    		return await TOOL_HANDLERS[toolName](request);
    	}
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 tool 'Ask a question to Tembo Docs,' which implies a read-only query operation, but doesn't clarify if it's a simple lookup, a semantic search, or an AI-generated response. It lacks details on rate limits, authentication needs, response format, or potential errors, leaving significant gaps in understanding how the tool 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 ('Ask a question to Tembo Docs') that efficiently conveys the core purpose without any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly. Every part of the sentence earns its place by specifying the action and target.

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 complexity (a query tool with no output schema and no annotations), the description is incomplete. It doesn't explain what kind of answers to expect, how results are formatted, or any behavioral traits like response time or data sources. Without annotations or an output schema, the description should provide more context to help the agent understand the tool's full scope and limitations.

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 the single parameter 'query' well-documented in the schema itself ('The ask query. For example, "how to create a Tembo instance"'). The description adds no additional meaning beyond what the schema provides, such as formatting tips or scope limitations. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 action ('Ask a question') and the target resource ('Tembo Docs'), which is specific enough to understand the tool's function. However, it doesn't differentiate itself from potential sibling tools like 'search_docs' or 'query_knowledge_base' that might exist in other contexts, though none are present in the provided sibling list.

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 an active Tembo instance), exclusions (e.g., not for technical support), or how it differs from other tools like 'get_instance' or 'get_all_instances' that might provide related information. Usage is implied but not explicitly defined.

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