Skip to main content
Glama

edubase_mcp_server_version

Read-onlyIdempotent

Retrieve the current version of the EduBase MCP server for debugging purposes.

Instructions

Get the MCP server version (only use for debugging).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:122-137 (registration)
    Registration of the 'edubase_mcp_server_version' tool on the MCP server with description and annotations.
    server.registerTool('edubase_mcp_server_version', {
    	description: 'Get the MCP server version (only use for debugging).',
    	annotations: {
    		title: 'Get MCP Server Version',
    		readOnlyHint: true,
    		destructiveHint: false,
    		idempotentHint: true,
    		openWorldHint: false,
    	},
    }, async (): Promise<CallToolResult> => {
    	/* Static response with server version, useful for testing connectivity and authentication */
    	return {
    		content: [{ type: 'text', text: VERSION }],
    		isError: false,
    	};
    });
  • Handler function that returns the server VERSION as text content, used for debugging connectivity and authentication.
    }, async (): Promise<CallToolResult> => {
    	/* Static response with server version, useful for testing connectivity and authentication */
    	return {
    		content: [{ type: 'text', text: VERSION }],
    		isError: false,
    	};
    });
  • The VERSION constant is read from package.json's version field and used by the tool handler.
    /* Version */
    const VERSION = packageJson.version;
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds only a debugging context, which is useful but does not contradict annotations. No further behavioral details needed.

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 sentence that is front-loaded and contains no unnecessary words. Every part earns its place.

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

Completeness5/5

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

For a simple version retrieval tool with no parameters and rich annotations, the description is complete. No output schema needed.

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?

No parameters exist; schema coverage is 100%. The description is not required to add parameter semantics. A baseline of 4 is appropriate.

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 states the verb 'Get' and the resource 'MCP server version', and adds the context 'only use for debugging'. This defines a specific purpose distinct from sibling tools.

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 says 'only use for debugging', providing a clear when-to-use guideline. No alternatives are mentioned, but the restriction is sufficient.

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/EduBase/MCP'

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