Skip to main content
Glama
La-fe
by La-fe

create_note

Create and store text notes with titles and content for organized documentation and information management.

Instructions

Create a new note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the note
contentYesText content of the note

Implementation Reference

  • The execution handler for the 'create_note' tool. It validates the title and content arguments, generates a new sequential ID, stores the note in the in-memory 'notes' object, and returns a text response confirming creation with the ID and title.
    case 'create_note': {
      const title = String(request.params.arguments?.title)
      const content = String(request.params.arguments?.content)
      if (!title || !content) {
        throw new Error('Title and content are required')
      }
    
      const id = String(Object.keys(notes).length + 1)
      notes[id] = { title, content }
    
      return {
        content: [
          {
            type: 'text',
            text: `Created note ${id}: ${title}`,
          },
        ],
      }
    }
  • Input JSON Schema for the 'create_note' tool, specifying an object with required 'title' and 'content' string properties.
    inputSchema: {
      type: 'object',
      properties: {
        title: {
          type: 'string',
          description: 'Title of the note',
        },
        content: {
          type: 'string',
          description: 'Text content of the note',
        },
      },
      required: ['title', 'content'],
    },
  • src/index.ts:103-120 (registration)
    Tool registration in the ListToolsRequestSchema handler response array, defining the name, description, and input schema for 'create_note'.
    {
      name: 'create_note',
      description: 'Create a new note',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'Title of the note',
          },
          content: {
            type: 'string',
            description: 'Text 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 full burden for behavioral disclosure. 'Create a new note' implies a write/mutation operation but doesn't specify permissions needed, whether creation is idempotent, error conditions, or what happens on success. For a mutation tool with zero annotation coverage, this is inadequate.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple creation tool and immediately communicates the core purpose without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error handling, or behavioral constraints. Given the complexity of a creation operation, more context about outcomes and limitations would be needed for the agent to use it effectively.

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?

Schema description coverage is 100%, with both parameters ('title' and 'content') fully documented in the schema. The description adds no additional parameter information beyond what the schema already provides, so it meets the baseline for high schema coverage without compensating value.

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 'Create a new note' clearly states the action (create) and resource (note), making the tool's purpose immediately understandable. It distinguishes from 'post_blog' and 'validate_blog' by focusing on notes rather than blogs, though it doesn't explicitly differentiate from 'write_note' which might be a similar operation.

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 'write_note' or 'post_blog'. There's no mention of prerequisites, appropriate contexts, or exclusions, leaving the agent to infer usage based on tool names alone.

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/La-fe/seo-mcp'

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