Skip to main content
Glama
9Ninety
by 9Ninety

getNote

Retrieve specific notes by their unique ID using this tool, designed to simplify access to recorded information on the MCP Notes server for efficient note management.

Instructions

Retrieves a specific note by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the note to retrieve

Implementation Reference

  • The handler function that implements the core logic of the getNote tool: retrieves a note from DynamoDB using GetCommand by ID and returns MCP-formatted content (JSON stringified note or not found message).
    export const handleGetNote = async (
      docClient: DynamoDBDocumentClient,
      tableName: string,
      id: string
    ) => {
      const command = new GetCommand({ TableName: tableName, Key: { id } });
      const response = await docClient.send(command);
      const note = response.Item as Note;
    
      return note
        ? {
            content: [
              { type: "text", text: `Note found with ID '${id}':` },
              { type: "text", text: JSON.stringify(note) },
            ],
          }
        : {
            content: [{ type: "text", text: `Note with ID '${id}' not found.` }],
          };
    };
  • Zod input schema for the getNote tool, validating a single 'id' string parameter.
    export const GetNoteInputSchema = z.object({
      id: z.string().describe("ID of the note to retrieve"),
    });
  • Tool object registration for getNote in the MCP tools list returned by getTools(), used for listTools handler. Converts Zod schema to JSON schema.
    {
      name: ToolName.GET_NOTE,
      description: "Retrieves a specific note by its ID.",
      inputSchema: zodToJsonSchema(GetNoteInputSchema) as Tool["inputSchema"],
    },
  • Dispatch/registration in the CallToolRequest handler switch statement: parses input with schema and invokes the getNote handler.
    case ToolName.GET_NOTE: {
      const { id: getNoteId } = GetNoteInputSchema.parse(args);
      return handleGetNote(docClient, tableName, getNoteId);
    }
  • Enum value defining the tool name constant ToolName.GET_NOTE = 'getNote'.
    GET_NOTE = "getNote",
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves a note, implying a read-only operation, but doesn't cover aspects like error handling (e.g., what happens if the ID is invalid), authentication needs, rate limits, or return format. This leaves gaps in understanding how the tool behaves beyond the basic action.

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 waste—it directly states the tool's purpose without redundancy. It's appropriately sized for a simple retrieval tool and front-loaded with the essential information.

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

Completeness3/5

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

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic action but lacks details on behavior, usage context, or output, which could be helpful for an agent. It meets the minimum viable standard but has clear gaps in completeness.

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 schema description coverage is 100%, with the parameter 'id' fully documented in the schema as 'ID of the note to retrieve'. The description adds no additional meaning beyond this, such as format examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 ('Retrieves') and resource ('a specific note by its ID'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like listNotes (which likely lists multiple notes) or deleteNote (which deletes), but the specificity of 'by its ID' implies it's for fetching a single, known note.

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 siblings like listNotes for browsing notes or writeNote for creating/updating, nor does it specify prerequisites (e.g., needing a valid note ID). Usage is implied by the action but lacks explicit context.

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/9Ninety/MCPNotes'

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