Skip to main content
Glama
jagoff

obsidian-mcp-complete

by jagoff

obsidian_rest_status

Read-only

Check whether the Obsidian Local REST API bridge is running and ready for use.

Instructions

Check the optional Obsidian Local REST API bridge status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the obsidian_rest_status tool. Checks if REST API is configured, returns the URL, and optionally pings the / endpoint if configured.
      "obsidian_rest_status",
      "Check the optional Obsidian Local REST API bridge status.",
      {},
      async () => ({
        configured: Boolean(config.restApiKey),
        url: config.restUrl,
        response: config.restApiKey ? await obsidianRestRequest(config, { path: "/" }) : undefined,
      }),
      { readOnlyHint: true },
    );
  • The schema/input for obsidian_rest_status is empty ({}) — no parameters needed.
    "obsidian_rest_status",
    "Check the optional Obsidian Local REST API bridge status.",
    {},
    async () => ({
  • src/tools.ts:1182-1191 (registration)
    Registration of the obsidian_rest_status tool via the tool() helper function inside registerObsidianTools().
      "obsidian_rest_status",
      "Check the optional Obsidian Local REST API bridge status.",
      {},
      async () => ({
        configured: Boolean(config.restApiKey),
        url: config.restUrl,
        response: config.restApiKey ? await obsidianRestRequest(config, { path: "/" }) : undefined,
      }),
      { readOnlyHint: true },
    );
  • The obsidianRestRequest helper function used by the handler to make the actual HTTP request to the Obsidian Local REST API.
    export async function obsidianRestRequest(config: ObsidianMcpConfig, options: RestRequestOptions): Promise<{
      status: number;
      ok: boolean;
      contentType: string;
      body: unknown;
    }> {
  • Config type defining restUrl and restApiKey fields used to check and configure the REST API bridge status.
    export type ObsidianMcpConfig = {
      vaults: VaultSpec[];
      defaultVault: string;
      readOnly: boolean;
      enableDelete: boolean;
      maxSearchResults: number;
      pretty: boolean;
      dailyFolder: string;
      dailyPattern: string;
      ragCommand: string;
      restUrl: string;
      restApiKey?: string;
      restInsecureTls: boolean;
      enableCommands: boolean;
      enableUiOpen: boolean;
    };
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds the nuance of 'optional' bridge, which is useful but does not disclose 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?

Single sentence, front-loaded, no filler. Every word adds value, earning its place.

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

Completeness3/5

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

For a simple status check with no output schema, the description could hint at the return format or common states. While adequate, it leaves the agent guessing about the response structure.

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 in schema (coverage 100%), so baseline is 4. The description need not add parameter details, and it correctly omits them.

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 action (check) and resource (Obsidian Local REST API bridge status). It is specific but does not differentiate from the sibling 'obsidian_status', leaving ambiguity about which status tool to use.

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 on when to use this tool versus alternatives like 'obsidian_status'. Missing context about prerequisites or typical scenarios, leaving the agent to infer usage.

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/jagoff/obsidian-mcp'

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