Skip to main content
Glama

get_server_info

Read-onlyIdempotent

Access server package metadata, runtime details, and tool inventory for a Minestom MCP server. Optionally include dependency versions.

Instructions

Use this when you need package metadata, runtime details, tool inventory, or knowledge-catalog coverage for this Minestom MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeDependenciesNoWhether to include runtime dependency versions in the response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
availableToolsYes
dependenciesNo
descriptionYes
knowledgeCatalogYes
nameYes
officialSourcesYes
runtimeYes
toolCountYes
versionYes

Implementation Reference

  • The main handler function 'createGetServerInfoTool' that defines the tool definition and executes the logic: parses input (includeDependencies), gets tool names, and returns server metadata including available tools, dependencies, knowledge catalog, runtime info, and version.
    export function createGetServerInfoTool(
    	getToolNames: () => string[],
    ): TanStackServerTool {
    	return toolDefinition({
    		description:
    			"Use this when you need package metadata, runtime details, tool inventory, or knowledge-catalog coverage for this Minestom MCP server.",
    		inputSchema: getServerInfoInputSchema,
    		name: "get_server_info",
    		outputSchema: getServerInfoOutputSchema,
    	}).server(async (args) => {
    		const { includeDependencies } = getServerInfoInputSchema.parse(args);
    		const availableTools = getToolNames();
    
    		return getServerInfoOutputSchema.parse({
    			availableTools,
    			dependencies: includeDependencies ? packageJson.dependencies : undefined,
    			description: packageJson.description,
    			knowledgeCatalog: {
    				coveredTopics: knowledgeCatalogMeta.coveredTopics,
    				environmentAwareTools: [
    					"inspect_minestom_environment",
    					"inspect_minestom_build",
    					"suggest_minestom_libraries",
    				],
    				supportsLiveLibraryLookup:
    					knowledgeCatalogMeta.supportsLiveLibraryLookup,
    				updatedOn: knowledgeCatalogMeta.updatedOn,
    				version: knowledgeCatalogMeta.version,
    			},
    			name: packageJson.name,
    			officialSources: knowledgeCatalogMeta.officialSources,
    			runtime: {
    				node: process.version,
    				platform: process.platform,
    			},
    			toolCount: availableTools.length,
    			version: packageJson.version,
    		});
    	});
    }
  • Input schema (getServerInfoInputSchema) and output schema (getServerInfoOutputSchema) for the get_server_info tool. Input accepts optional 'includeDependencies' boolean. Output includes availableTools, dependencies, description, knowledgeCatalog, name, officialSources, runtime, toolCount, and version.
    const getServerInfoInputSchema = z.object({
    	includeDependencies: z
    		.boolean()
    		.default(false)
    		.describe(
    			"Whether to include runtime dependency versions in the response.",
    		),
    });
    
    const getServerInfoOutputSchema = z.object({
    	availableTools: z.array(z.string()),
    	dependencies: z.record(z.string(), z.string()).optional(),
    	description: z.string(),
    	knowledgeCatalog: z.object({
    		coveredTopics: z.array(minestomTopicSchema),
    		environmentAwareTools: z.array(z.string()),
    		supportsLiveLibraryLookup: z.boolean(),
    		updatedOn: z.string(),
    		version: z.string(),
    	}),
    	name: z.string(),
    	officialSources: z.array(officialLinkSchema),
    	runtime: z.object({
    		node: z.string(),
    		platform: z.string(),
    	}),
    	toolCount: z.number().int(),
    	version: z.string(),
    });
  • src/tools.ts:15-28 (registration)
    Registration of the get_server_info tool: createGetServerInfoTool is called with a getToolNames callback that maps tool names from the tools array, then the result is pushed into the tools array.
    const tools: TanStackServerTool[] = [];
    const toolNames = () => tools.map((tool) => tool.name);
    
    tools.push(
    	pingTool,
    	createGetServerInfoTool(toolNames),
    	inspectMinestomEnvironmentTool,
    	inspectMinestomBuildTool,
    	explainMinestomPatternTool,
    	lookupMinestomApiTool,
    	planMinestomFeatureTool,
    	reviewMinestomDesignTool,
    	suggestMinestomLibrariesTool,
    );
  • src/server.ts:8-97 (registration)
    Top-level server setup: tools are registered with the MCP server via registerTanStackTools, which calls registerTanStackTool for each tool (including get_server_info).
    (async () => {
    	console.error("Starting MineStom MCP server...");
    	const server = new McpServer({
    		name: "minestom-mcp",
    		description: packageJson.description,
    		version: packageJson.version,
    	});
    
    	registerTanStackTools(server, serverTools);
    
    	const transport = new StdioServerTransport();
    	await server.connect(transport);
    	console.error(
    		`MineStom server started with ${serverTools.length} tools, running through stdio.`,
    	);
    
    	process.on("uncaughtException", (err) => console.error(err));
    	process.on("exit", () => console.error("Shutting down MineStom MCP server."));
    	process.on("beforeExit", () => server.close());
    	process.on("SIGINT", () => process.exit());
    	process.on("SIGTERM", () => process.exit());
    })();
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by specifying the types of data returned but does not disclose additional behavioral traits beyond what annotations provide.

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?

A single, well-structured sentence that directly states the tool's purpose with no unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and the description covers the main use cases, it is sufficiently complete for an information-retrieval tool, though it could mention the response structure or defaults.

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?

Schema coverage is 100% and the single boolean parameter is well-described in the schema; the description adds no further parameter information beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly lists the specific types of information the tool provides (package metadata, runtime details, etc.), distinguishing it from sibling tools that focus on specific Minestom aspects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly starts with 'Use this when you need...', providing clear guidance on when to invoke the tool, though it does not explicitly mention when not to use it or list alternatives.

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

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/Azoraqua/minestom-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server