Skip to main content
Glama
bezata

kObsidian MCP

Server Version

system.version
Read-onlyIdempotent

Retrieve the kObsidian server's package name, version, runtime, and runtime version to perform health checks or confirm the server build. Read-only, zero side effects.

Instructions

Return the running kObsidian server's package name, semver version, host runtime (bun or node), and runtime version. Use this as a health-check or to confirm which server build a client is talking to. Read-only; zero side effects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesnpm package name of the running server.
versionYesSemver version.
runtimeYesWhich runtime is executing the server.
runtimeVersionYesVersion of the runtime (bun or node).
summaryYesHuman-readable one-liner combining the fields above.

Implementation Reference

  • The actual handler function for the system.version tool. Returns package name, version, runtime info, and a summary string.
    handler: async () => {
      const runtime: "bun" | "node" = isBun ? "bun" : "node";
      const runtimeVersion = isBun
        ? ((process.versions as { bun?: string }).bun ?? "unknown")
        : process.version;
      return {
        name: PACKAGE_NAME,
        version: PACKAGE_VERSION,
        runtime,
        runtimeVersion,
        summary: `${PACKAGE_NAME} ${PACKAGE_VERSION} on ${runtime} ${runtimeVersion}`,
      };
    },
  • Output schema (versionOutputSchema) defining the shape returned by system.version: name, version, runtime, runtimeVersion, summary.
    const versionOutputSchema = z
      .object({
        name: z.string().describe("npm package name of the running server."),
        version: z.string().describe("Semver version."),
        runtime: z.enum(["bun", "node"]).describe("Which runtime is executing the server."),
        runtimeVersion: z.string().describe("Version of the runtime (bun or node)."),
        summary: z.string().describe("Human-readable one-liner combining the fields above."),
      })
      .describe("Return shape for `system.version`.");
  • Tool definition registration including the name 'system.version', title, description, input/output schemas, and annotations.
    export const systemTools: ToolDefinition[] = [
      {
        name: "system.version",
        title: "Server Version",
        description:
          "Return the running kObsidian server's package name, semver version, host runtime (`bun` or `node`), and runtime version. Use this as a health-check or to confirm which server build a client is talking to. Read-only; zero side effects.",
        inputSchema: z.object({}).strict(),
        outputSchema: versionOutputSchema,
        annotations: READ_ONLY,
        handler: async () => {
          const runtime: "bun" | "node" = isBun ? "bun" : "node";
          const runtimeVersion = isBun
            ? ((process.versions as { bun?: string }).bun ?? "unknown")
            : process.version;
          return {
            name: PACKAGE_NAME,
            version: PACKAGE_VERSION,
            runtime,
            runtimeVersion,
            summary: `${PACKAGE_NAME} ${PACKAGE_VERSION} on ${runtime} ${runtimeVersion}`,
          };
        },
      },
    ];
  • The toolRegistry array that collects all tool definitions including systemTools (which contains system.version).
    export const toolRegistry: ToolDefinition[] = [
      ...vaultTools,
      ...noteTools,
      ...tagTools,
      ...linkTools,
      ...analyticsTools,
      ...taskTools,
      ...dataviewTools,
      ...blocksTools,
      ...marpTools,
      ...kanbanTools,
      ...canvasTools,
      ...templateTools,
      ...apiTools,
      ...wikiTools,
      ...systemTools,
    ];
  • Where each tool in toolRegistry (including system.version) is registered with the MCP server via server.registerTool.
      for (const tool of toolRegistry) {
        server.registerTool(
          tool.name,
          {
            title: tool.title,
            description: buildDescription(tool),
            inputSchema: tool.inputSchema ?? z.object({}),
            outputSchema: tool.outputSchema,
            ...(tool.annotations ? { annotations: tool.annotations } : {}),
          },
          async (args) => {
            try {
              const result = (await tool.handler(context, args)) as Record<string, unknown>;
              return ok(result, getSummary(result) ?? `${tool.title} completed`);
            } catch (error) {
              const appError = toAppError(error);
              throw new Error(formatErrorMessage(appError));
            }
          },
        );
      }
    
      registerWikiResources(server, context);
      registerWikiPrompts(server);
    
      return server;
    }
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds 'zero side effects' and details the return values, providing behavioral context beyond the annotations. No contradictions.

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?

Two short sentences: the first describes return content, the second states purpose and safety. No wasted words; perfectly front-loaded.

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?

Given no input parameters and the existence of an output schema, the description fully covers what the tool does and when to use it. No gaps remain.

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 are present, so the description does not need to explain them. The baseline is 4 for zero parameters, and the description adds no redundant information.

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 tool returns the running kObsidian server's package name, semver version, host runtime, and runtime version. It uniquely identifies this as a version/health-check tool, distinguishing it from sibling tools which are focused on content operations.

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?

Explicitly states to use as a health-check or to confirm which server build a client is talking to. It also notes read-only and zero side effects, guiding appropriate usage. Lacks explicit when-not alternatives, but its simplicity makes that unnecessary.

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/bezata/kObsidian'

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