Skip to main content
Glama
bishnubista

Vulnerable Notes MCP Server

by bishnubista

notes_create

Create new notes with specified titles and content using this tool from the Vulnerable Notes MCP Server, which demonstrates security vulnerabilities for testing and training purposes.

Instructions

Create a new note with the given title and content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the note
contentYesContent of the note

Implementation Reference

  • The implementation of the notes_create tool handler. It takes a title and content, ensures the notes directory exists, and writes the note content to a Markdown file.
    case "notes_create": {
      const { title, content } = args as { title: string; content: string };
      const filePath = getNotePath(title);
    
      // Ensure directory exists
      if (!fs.existsSync(NOTES_DIR)) {
        fs.mkdirSync(NOTES_DIR, { recursive: true });
      }
    
      fs.writeFileSync(filePath, content);
      return {
        content: [{ type: "text", text: `Note "${title}" created successfully` }],
      };
    }
  • The registration and schema definition for the notes_create tool, including its name, description, and input parameters.
    {
      name: "notes_create",
      description: "Create a new note with the given title and content",
      inputSchema: {
        type: "object" as const,
        properties: {
          title: { type: "string", description: "Title of the note" },
          content: { type: "string", description: "Content of the note" },
        },
        required: ["title", "content"],
      },
    },
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. While 'Create' implies a write operation, the description fails to disclose idempotency behavior, what happens if a note with the same title exists, or what the tool returns upon completion.

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 with no waste. The core action is front-loaded ('Create a new note') followed immediately by the parameter reference. Every word earns 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?

Given the simplicity (2 parameters, no nested objects, no output schema), the description covers the minimum necessary. However, without annotations or output schema, it should ideally mention return behavior or side effects (e.g., ID generation, confirmation) to be fully complete.

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

Parameters3/5

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

The description references 'title and content' which maps to the two parameters, but with 100% schema description coverage already providing clear definitions ('Title of the note', 'Content of the note'), the description adds no additional semantic value beyond naming the parameters.

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 (Create) and resource (note), distinguishing it from sibling tools like notes_delete, notes_read, and search_notes through the action-oriented language. However, it doesn't explicitly differentiate from potential update or duplicate scenarios.

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 provided on when to use this tool versus alternatives (e.g., when to create vs. update, or whether to check for existing notes first). No prerequisites or conditions mentioned.

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/bishnubista/vulnerable-notes-mcp'

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