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

write_note

Create and store text notes with title and content for organized documentation and information capture.

Instructions

Write a new note

Input Schema

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

Implementation Reference

  • The execution handler for the 'write_note' tool. Extracts title and content from input arguments, validates presence, assigns a new sequential ID, stores the note in the in-memory 'notes' dictionary, and returns a textual success response.
    case 'write_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: `Wrote note ${id}: ${title}`,
          },
        ],
      }
    }
  • Input schema for the 'write_note' tool defining the expected object structure 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:121-138 (registration)
    The tool registration entry in the list of available tools returned by ListToolsRequestHandler, specifying name, description, and input schema for 'write_note'.
    {
      name: 'write_note',
      description: 'Write 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. 'Write a new note' implies a creation/mutation operation but doesn't specify permissions needed, whether the note is saved permanently, what happens on failure, or any rate limits. 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 extremely concise - just three words that directly state the tool's function. There's zero wasted language, and the meaning is immediately clear despite its brevity. This is an example of efficient communication.

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 happens after writing the note (where it's stored, what format it returns, error conditions). Given the complexity of a write operation and lack of structured metadata, more context is needed.

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 adds no parameter information beyond what's already in the schema (which has 100% coverage). Both parameters (title and content) are fully documented in the schema with clear descriptions. The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

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

Purpose3/5

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

The description 'Write a new note' clearly states the action (write) and resource (note), but it's quite basic and doesn't distinguish from the sibling tool 'create_note' which appears to serve a similar purpose. The description is functional but lacks specificity about what makes this tool different from its sibling.

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 the sibling 'create_note' or other related tools like 'post_blog' and 'validate_blog'. There's no mention of prerequisites, alternatives, or appropriate contexts for selecting this specific tool.

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