Skip to main content
Glama
tembo-io

Tembo MCP Server

Official
by tembo-io

get_instance_schema

Retrieve the JSON schema for an instance to define and validate its structure with the Tembo MCP Server, enabling precise management of Tembo Cloud resources.

Instructions

Get the json-schema for an instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_instance_schema' tool. It calls temboClient.getSchema() and returns the JSON-stringified response as text content.
    get_instance_schema: async () => {
    	const response = await temboClient.getSchema();
    	return {
    		content: [
    			{
    				type: "text",
    				text: JSON.stringify(response.data ?? response.error, null, 2),
    			},
    		],
    	};
    },
  • src/tools.ts:51-58 (registration)
    Registration of the 'get_instance_schema' tool in the TOOLS array, including name, description, and input schema (no required parameters).
    {
    	name: "get_instance_schema" as const,
    	description: "Get the json-schema for an instance",
    	inputSchema: {
    		type: "object",
    		properties: {},
    	},
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states it 'gets' data, implying a read-only operation, but doesn't disclose behavioral traits like whether it requires authentication, has rate limits, returns structured data, or any error conditions. The description is minimal and lacks necessary context for safe use.

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 that directly states the tool's function. It's front-loaded with the core action and resource, with zero wasted words, making it highly concise and well-structured.

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 complexity (a tool to retrieve schema data) and lack of annotations or output schema, the description is incomplete. It doesn't explain what the json-schema contains, how it's formatted, or what the return value looks like, leaving significant gaps for an AI agent to use it correctly.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, but it could briefly mention that no inputs are required. Baseline is 4 for 0 parameters, as it doesn't need to compensate for gaps.

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 ('json-schema for an instance'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_instance' or 'get_all_instances' which might also retrieve instance-related data but of different types.

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. It doesn't mention prerequisites, context for needing the schema, or how it differs from other 'get' operations like 'get_instance' or 'get_all_instances' in the sibling list.

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