Skip to main content
Glama
takuya0206

Obsidian MCP

by takuya0206

readActiveNote

Retrieve the content of your currently open note in Obsidian to access information for AI-assisted tasks.

Instructions

Read the contents of the current active note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main tool handler factory function that creates the executor for the 'readActiveNote' tool. It calls the ObsidianAPI's readActiveNote method and formats the success or error response.
    export function createReadActiveNoteTool(api: ObsidianAPI): ToolHandler {
      return async (): Promise<ToolResponse> => {
        try {
          const note = await api.readActiveNote();
          return formatSuccessResponse(note);
        } catch (error) {
          return formatErrorResponse(`Error reading active note: ${(error as Error).message}`);
        }
      };
    }
  • The tool definition including name, description, and schema (empty object for no parameters). The schema is defined earlier as ReadActiveNoteSchema = {}.
    export const readActiveNoteDefinition: ToolDefinition = {
      name: "readActiveNote",
      description: "Read the contents of the current active note",
      schema: ReadActiveNoteSchema
    };
  • src/server.ts:56-60 (registration)
    Registers the 'readActiveNote' tool with the MCP server by calling server.tool with the definition and the created handler.
      readActiveNoteDefinition.name,
      readActiveNoteDefinition.description,
      readActiveNoteDefinition.schema,
      createReadActiveNoteTool(this.api)
    );
  • The underlying API method in ObsidianAPI that performs the HTTP GET request to retrieve the active note contents.
    async readActiveNote(): Promise<NoteJson> {
      const response = await this.client.get(`/active/`, {
        headers: {
          ...this.defaultHeaders,
          "Content-Type": "application/json",
          accept: "application/vnd.olrapi.note+json",
        },
      });
      return response.data as NoteJson;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation but doesn't clarify what 'active note' means, whether it returns structured data or plain text, or if there are any side effects. This leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'active note' entails, what format the contents are returned in, or how this differs from sibling tools. For a tool with no structured data to rely on, more context is 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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary information.

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 verb ('Read') and resource ('contents of the current active note'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'readNote' or 'listNotes', which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives like 'readNote' or 'listNotes'. It doesn't specify prerequisites (e.g., whether a note must be actively open) or contextual constraints, leaving usage ambiguous.

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

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