Skip to main content
Glama
truaxki

MCP Notes Server

by truaxki

list-all-notes

Retrieve all stored notes from the MCP Notes Server to access, manage, or review your persisted data efficiently using this tool.

Instructions

Read all stored notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that executes the list-all-notes tool by fetching all notes from storage, formatting them, and returning a formatted text content list.
    async def _handle_list_notes(self) -> List[types.TextContent]:
        """Process note listing requests."""
        notes = self.storage.get_all_notes()
        if not notes:
            return [
                types.TextContent(
                    type="text",
                    text="No notes stored yet.",
                )
            ]
        
        notes_text = "\n".join(
            f"- {name}:\n"
            f"  Content: {note['content']}\n"
            f"  Created: {note['created_at']}\n"
            f"  Modified: {note['modified_at']}"
            for name, note in notes.items()
        )
        return [
            types.TextContent(
                type="text",
                text=f"All stored notes:\n{notes_text}",
            )
        ]
  • Defines the tool schema with empty input properties (no arguments required) and description for list-all-notes.
    types.Tool(
        name="list-all-notes",
        description="Read all stored notes",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • MCP registration endpoint for listing tools, which includes the list-all-notes tool schema via tool_list.get_tool_list().
    @server.list_tools()
    async def handle_list_tools() -> list[types.Tool]:
        """Return list of available note management tools."""
        return tool_list.get_tool_list()
  • Tool dispatch registration in the handler class that routes 'list-all-notes' calls to the specific handler method.
    async def handle_tool(self, name: str, arguments: Optional[Dict]) -> List[types.TextContent]:
        """Route tool requests to appropriate handlers."""
        if name == "add-note":
            return await self._handle_add_note(arguments)
        elif name == "update-note":
            return await self._handle_update_note(arguments)
        elif name == "delete-note":
            return await self._handle_delete_note(arguments)
        elif name == "list-all-notes":
            return await self._handle_list_notes()
        else:
            raise ValueError(f"Unknown tool: {name}")
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'Read all stored notes,' which implies a safe, read-only operation, but fails to add context like whether it returns all notes at once, uses pagination, requires authentication, or has rate limits. This leaves significant gaps in understanding the tool's behavior.

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 'Read all stored notes' is a single, efficient sentence that front-loads the core purpose with zero waste. It is appropriately sized for a simple tool, making it easy for an agent to parse and understand quickly.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states the basic action but lacks details on behavior (e.g., return format, pagination) that would be helpful for a read operation, especially without annotations to cover safety or performance aspects.

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 schema description coverage at 100%, so no parameter documentation is needed. The description appropriately doesn't mention parameters, aligning with the schema, and thus meets the baseline for a parameterless tool without adding unnecessary details.

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 'Read all stored notes' clearly states the verb ('Read') and resource ('all stored notes'), making the tool's purpose immediately understandable. It distinguishes from siblings like 'add-note' or 'delete-note' by specifying a read-only operation, though it doesn't explicitly contrast with potential filtering alternatives beyond the scope of siblings.

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 lacks context such as prerequisites, timing, or comparisons to other tools (e.g., if there are filtering options not listed as siblings), leaving the agent with minimal usage direction beyond the basic purpose.

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/truaxki/mcp-notes'

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