Skip to main content
Glama
Sign In
mcp-knowledge-base

mcp-knowledge-base

by vishnu-vasan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_note

Retrieve a specific note from your knowledge base by providing its unique ID. Returns the note content if found, otherwise returns null.

Instructions

Retrieve a single note by ID.

Args: note_id: The unique ID of the note.

Returns: The note if found, or None.

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": {
      "note_id": "<note_id>"
    },
    "name": "get_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states 'Returns: The note if found, or None,' which clearly communicates the behavior when the note is missing. It also uses 'Retrieve' to imply a read-only operation, adding useful 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, using a standard Args/Returns format. Every sentence adds value, and there is no redundant information. It is front-loaded with the action and purpose.

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

Completeness4/5

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

This is a simple single-parameter tool with an output schema available. The description covers the essential behavior, including the not-found case, and is complete enough for an agent to use correctly. A slightly more explicit usage guideline would have made it fully complete.

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?

Schema description coverage is 0%, so the description must compensate. It explains 'note_id: The unique ID of the note,' which adds semantic meaning beyond the schema's plain 'integer' type and title. This fully clarifies the parameter's purpose.

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

Purpose5/5

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

The description clearly states 'Retrieve a single note by ID.' This is a specific verb+resource pair that distinguishes it from sibling tools like list_notes (all notes) and search_notes (search). It unambiguously indicates the operation.

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

Usage Guidelines3/5

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

The description implies usage when you have a note ID and need a single note, but it does not explicitly contrast with alternatives or state when not to use it. No exclusions or alternative suggestions are provided.

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