Skip to main content
Glama
bezata

kObsidian MCP

Server Version

system.version
Read-onlyIdempotent

Retrieve the kObsidian server's package name, semver version, and runtime details for health checks. Read-only with 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 handler function for system.version tool. It returns package name, version, runtime (bun/node), runtime version, and a human-readable summary.
      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 definition for system.version, validating the returned object with name, version, runtime, runtimeVersion, and summary fields.
    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`.");
  • Registration of the system.version tool as part of the systemTools array, defining name, title, description, input/output schemas, annotations, and handler.
    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}`,
          };
        },
      },
    ];
  • Global tool registry that imports and spreads systemTools (including system.version) into the combined tool list.
    export const toolRegistry: ToolDefinition[] = [
      ...vaultTools,
      ...noteTools,
      ...tagTools,
      ...linkTools,
      ...analyticsTools,
      ...taskTools,
      ...dataviewTools,
      ...blocksTools,
      ...marpTools,
      ...kanbanTools,
      ...canvasTools,
      ...templateTools,
      ...apiTools,
      ...wikiTools,
      ...systemTools,
    ];
  • Helper that reads PACKAGE_NAME and PACKAGE_VERSION from package.json, used by the handler to populate name and version fields.
    import pkg from "../../package.json" with { type: "json" };
    
    export const PACKAGE_NAME: string = pkg.name;
    export const PACKAGE_VERSION: string = pkg.version;
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description reinforces with 'Read-only; zero side effects' and adds detail about return fields, but 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 sentences, front-loaded with return value, efficient. Every sentence adds value.

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?

Tool has no parameters, output schema exists, annotations complete. Description fully covers what the agent needs to know for correct invocation.

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, schema coverage 100%. Description adds no extra parameter info needed, baseline 4 applies.

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?

Description explicitly states the tool returns package name, semver, host runtime, and runtime version. The verb 'Return' and resource 'running kObsidian server' clearly define purpose. Distinguishes from siblings as a server-level version/health check.

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?

Provides explicit use cases: health-check or confirming server build. No alternative tools are mentioned, but the description is sufficient for a parameterless tool.

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