Skip to main content
Glama
binodrajpandey

MCP Server Example

delete_note

Remove a note from storage by specifying its name to manage your data efficiently.

Instructions

Delete a note by name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:39-45 (handler)
    The delete_note tool handler function. Takes a note name as parameter, checks if it exists in the in-memory notes dictionary, deletes it if found, and returns a status message. Decorated with @mcp.tool() which also serves as the registration.
    @mcp.tool()
    def delete_note(name: str) -> str:
        """Delete a note by name."""
        if name not in notes:
            return f"Note '{name}' not found."
        del notes[name]
        return f"Note '{name}' deleted."
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes a note, implying a destructive mutation, but doesn't cover critical aspects like permissions needed, whether deletion is reversible, error handling, or confirmation requirements. 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 is a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for conciseness.

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 destructive tool with no annotations, 0% schema coverage, and an output schema (which helps but isn't described), the description is incomplete. It lacks details on behavior, parameters, and usage context, making it inadequate for safe and effective tool invocation by an agent.

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?

Schema description coverage is 0%, and the description only mentions 'by name' without explaining what 'name' refers to (e.g., note title, ID, filename), its format, or constraints. With one undocumented parameter, the description fails to compensate for the lack of schema details, providing minimal semantic value.

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 ('Delete') and resource ('a note'), making the purpose unambiguous. It doesn't distinguish from siblings like 'save_note', but it's specific enough to understand the basic function without being tautological.

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?

No guidance is provided on when to use this tool versus alternatives like 'save_note' or other sibling tools. The description only states what it does, not when it should be selected, leaving the agent without context for decision-making.

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

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/binodrajpandey/mcp-example'

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