Skip to main content
Glama
Sign In
NotesKeep MCP Server

NotesKeep MCP Server

by mariomosca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_note_labels

Retrieve labels associated with a specific note to organize and categorize your content within the NotesKeep MCP Server.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "noteId": "<noteId>"
    },
    "name": "get_note_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYesID of the note

Implementation Reference

  • src/index.ts:472-497 (handler)
    The tool 'get_note_labels' is registered and implemented in src/index.ts. It takes a noteId as input, calls an API to fetch the labels for that note, and returns them as a JSON string.
    server.tool(
    "get_note_labels",
    {
        noteId: z.number().describe("ID of the note"),
    },
    async ({ noteId }) => {
        try {
            const data = await apiRequest(`/api/notes/${noteId}/labels`);

            return {
                content: [{
                    type: "text",
                    text: JSON.stringify(data.labels, null, 2)
                }]
            };
        } catch (error) {
            return {
                content: [{
                    type: "text",
                    text: `Error getting note labels: ${error}`
                }],
                isError: true
            };
        }
    }
);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools