Skip to main content
Glama

list_user_notes

Retrieve all notes owned by the user using the HackMD API. This tool helps organize and manage personal notes efficiently through the MCP server.

Instructions

List all notes owned by the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the list_user_notes tool. It fetches the user's notes using the HackMD API client.getNoteList(), stringifies them as JSON, and returns as text content block. Handles errors by returning an error message.
    async () => {
      try {
        const notes = await client.getNoteList();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(notes, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Registers the list_user_notes tool with the MCP server, specifying name, description, empty input schema, output hints (read-only, open-world), and attaches the handler function.
    server.tool(
      "list_user_notes",
      "List all notes owned by the user",
      {},
      {
        title: "Get a list of notes in the user's workspace",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async () => {
        try {
          const notes = await client.getNoteList();
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(notes, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • tools/index.ts:21-21 (registration)
    Top-level call to register all user notes tools, including list_user_notes, within the registerAllTools function.
    registerUserNotesApiTools(server, client);
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. It states it's a list operation but doesn't describe return format, pagination, sorting, error conditions, or authentication requirements. 'List all notes' implies it might return a potentially large dataset without filtering options, but this isn't explicitly stated.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose and doesn't include unnecessary elaboration. Every word earns its place in conveying the essential function.

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 tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'notes' are, what fields they contain, how they're formatted, or what 'owned by the user' means operationally. The agent would need to guess about the return structure and behavioral characteristics.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, earning a baseline 4 for not creating confusion about non-existent 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 ('List') and resource ('notes owned by the user'), making the purpose immediately understandable. It distinguishes from sibling tools like 'list_team_notes' by specifying 'user' scope, though it doesn't explicitly contrast with 'list_team_notes' in the description text itself.

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 'list_team_notes' or 'get_note'. It doesn't mention prerequisites, limitations, or typical use cases, leaving the agent to infer usage from the name 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

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/yuna0x0/hackmd-mcp'

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