Skip to main content
Glama
bscott

NotePlan MCP Server

by bscott

get_notes_by_folder

Retrieve notes from a specific folder in NotePlan to organize and access your content efficiently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderYesThe folder name to search in

Implementation Reference

  • src/index.ts:73-89 (registration)
    MCP server tool registration for 'get_notes_by_folder', including Zod input schema and thin wrapper handler delegating to noteService.getNotesByFolder.
    server.tool(
      'get_notes_by_folder',
      {
        folder: z.string().describe('The folder name to search in'),
      },
      async ({ folder }) => {
        const notes = noteService.getNotesByFolder(folder);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(notes, null, 2),
            },
          ],
        };
      }
    );
  • Core implementation of getNotesByFolder: filters the cached list of all notes by exact folder match or prefix (for subfolders).
    function getNotesByFolder(folder: string): Note[] {
      const notes = getAllNotes();
      return notes.filter(note => note.folder === folder || note.folder.startsWith(folder + '/'));
    }
  • Zod input schema for the tool, validating the 'folder' parameter as a string.
    {
      folder: z.string().describe('The folder name to search in'),
    },
  • src/index.js:69-81 (registration)
    Alternative REST API endpoint registration/dispatch for getNotesByFolder command in the JS server implementation.
    case 'getNotesByFolder':
      if (!args.folder) {
        return res.status(400).json({ 
          error: 'Missing required parameter: folder', 
          status: 'error' 
        });
      }
        
      return res.json({ 
        result: noteService.getNotesByFolder(args.folder),
        status: 'success' 
      });
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/bscott/noteplan-mcp'

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