Skip to main content
Glama

Create Note

create_note

Generate a micro-note with customizable privacy settings (public or private) to store concise information efficiently. Integrates with Emlog MCP Server for streamlined content management.

Instructions

Create a new micro-note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
privateNoWhether the note is private (y) or public (n)
tYesThe content of the micro-note

Implementation Reference

  • MCP tool handler for 'create_note': calls emlogClient.publishNote with input parameters and returns a formatted success or error message.
    async ({ t, private: isPrivate }) => {
      try {
        await emlogClient.publishNote(t, isPrivate);
        return {
          content: [{
            type: "text",
            text: `Successfully created micro-note: ${t.substring(0, 50)}${t.length > 50 ? '...' : ''}`
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error: ${error instanceof Error ? error.message : String(error)}`
          }],
          isError: true
        };
      }
    }
  • Zod input schema defining parameters 't' (note content) and optional 'private' flag for the create_note tool.
    inputSchema: {
      t: z.string().describe("The content of the micro-note"),
      private: z.enum(["y", "n"]).optional().describe("Whether the note is private (y) or public (n)")
    }
  • src/index.ts:482-511 (registration)
    Registration of the 'create_note' tool using server.registerTool, including schema and inline handler function.
    server.registerTool(
      "create_note",
      {
        title: "Create Note",
        description: "Create a new micro-note",
        inputSchema: {
          t: z.string().describe("The content of the micro-note"),
          private: z.enum(["y", "n"]).optional().describe("Whether the note is private (y) or public (n)")
        }
      },
      async ({ t, private: isPrivate }) => {
        try {
          await emlogClient.publishNote(t, isPrivate);
          return {
            content: [{
              type: "text",
              text: `Successfully created micro-note: ${t.substring(0, 50)}${t.length > 50 ? '...' : ''}`
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • EmlogClient.publishNote method: constructs form data with note content and privacy flag, posts to Emlog API endpoint /?rest-api=note_post to create the note.
    async publishNote(content: string, isPrivate?: string): Promise<{ note_id: number }> {
      const note = {
        t: content,
        private: isPrivate || 'n'
      };
      const formData = this.buildFormData(note);
      const response = await this.api.post('/?rest-api=note_post', formData);
      return response.data.data;
    }
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 'Create a new micro-note', implying a write/mutation operation, but doesn't disclose any behavioral traits such as permissions required, whether notes are ephemeral or persistent, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 with a single sentence ('Create a new micro-note') that directly states the purpose without any fluff. It is front-loaded and wastes no words, making it efficient for quick understanding. Every word earns its place by conveying essential action and resource information.

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 tool's mutation nature (creating a note), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects, error handling, or return values, which are critical for an agent to use the tool correctly. The high schema coverage helps with parameters, but overall context for safe and effective usage is lacking.

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 clear descriptions for both parameters ('t' as content, 'private' with enum values). The description adds no parameter semantics beyond what the schema provides, as it doesn't mention parameters at all. Given high schema coverage, the baseline score of 3 is appropriate, as the schema adequately documents parameters without needing description supplementation.

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 action ('Create') and resource ('new micro-note'), making the purpose immediately understandable. It distinguishes from siblings like 'add_comment' or 'create_article' by specifying 'micro-note' as the resource type. However, it doesn't explicitly differentiate from 'create_article' beyond the resource name, missing a clear distinction in scope or format.

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. It doesn't mention when to choose 'create_note' over 'create_article' or 'add_comment', nor does it specify prerequisites, contexts, or exclusions for usage. This leaves the agent without explicit direction for tool selection among siblings.

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

Related 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/eraincc/emlog-mcp'

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