Skip to main content
Glama
bossjones

Datetime MCP Server

by bossjones

add-note

Create and store a new note with a name and content in the Datetime MCP Server's note management system.

Instructions

Add a new note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
contentYes

Implementation Reference

  • The handler logic for the 'add-note' tool within the handle_call_tool function. It validates the input arguments, stores the note in the global 'notes' dictionary, notifies connected clients about resource changes, and returns a confirmation TextContent.
    if name == "add-note":
        if not arguments:
            raise ValueError("Missing arguments")
    
        note_name = arguments.get("name")
        content = arguments.get("content")
    
        if not note_name or not content:
            raise ValueError("Missing name or content")
    
        # Update server state
        notes[note_name] = content
    
        # Notify clients that resources have changed - only if in a request context
        try:
            await server.request_context.session.send_resource_list_changed()
        except LookupError:
            # Running outside of a request context (e.g., in tests)
            pass
    
        return [
            types.TextContent(
                type="text",
                text=f"Added note '{note_name}' with content: {content}",
            )
        ]
  • The JSON schema definition for the 'add-note' tool, including required properties 'name' and 'content', registered in the handle_list_tools function.
    types.Tool(
        name="add-note",
        description="Add a new note",
        inputSchema={
            "type": "object",
            "properties": {
                "name": {"type": "string"},
                "content": {"type": "string"},
            },
            "required": ["name", "content"],
        },
    ),
  • The tool registration in the handle_list_tools function, which returns a list of available tools including 'add-note'.
    return [
        types.Tool(
            name="add-note",
            description="Add a new note",
            inputSchema={
                "type": "object",
                "properties": {
                    "name": {"type": "string"},
                    "content": {"type": "string"},
                },
                "required": ["name", "content"],
            },
        ),
        types.Tool(
            name="get-current-time",
            description="Get the current time in various formats",
            inputSchema={
                "type": "object",
                "properties": {
                    "format": {
                        "type": "string",
                        "enum": ["iso", "readable", "unix", "rfc3339"],
                        "description": "Format to return the time in"
                    },
                    "timezone": {
                        "type": "string",
                        "description": "Optional timezone (default: local system timezone)"
                    }
                },
                "required": ["format"]
            }
        ),
        types.Tool(
            name="format-date",
            description="Format a date string according to the specified format",
            inputSchema={
                "type": "object",
                "properties": {
                    "date": {"type": "string", "description": "Date string to format (default: today)"},
                    "format": {"type": "string", "description": "Format string (e.g., '%Y-%m-%d %H:%M:%S')"}
                },
                "required": ["format"]
            }
        )
    ]
Behavior1/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. 'Add a new note' implies a write operation, but it doesn't disclose any behavioral traits such as permissions required, whether the note is saved permanently, if there are rate limits, or what happens on success/failure. This is a significant gap for a mutation tool with zero annotation coverage.

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 with 'Add a new note'—a single, front-loaded sentence that wastes no words. It efficiently conveys the core action without unnecessary elaboration, making it easy to parse quickly.

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?

Given the tool's complexity (a write operation with 2 parameters), lack of annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't provide enough context for an AI agent to use the tool effectively, missing details on behavior, parameters, and outcomes.

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

Parameters2/5

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

The schema description coverage is 0%, meaning parameters 'name' and 'content' are undocumented in the schema. The description adds no meaning beyond the schema—it doesn't explain what 'name' and 'content' represent, their formats, or constraints. This fails to compensate for the low coverage, leaving parameters poorly understood.

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

Purpose3/5

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

The description 'Add a new note' clearly states the action (add) and resource (note), making the basic purpose understandable. However, it doesn't specify what kind of note (e.g., text note, annotation, comment) or distinguish it from potential sibling tools (though the actual siblings are unrelated time/date tools). This leaves the purpose somewhat vague but adequate.

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 prerequisites, context (e.g., adding notes to what system or entity), or exclusions. With sibling tools being unrelated (format-date, get-current-time), there's no explicit comparison, leaving usage unclear.

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/bossjones/datetime-mcp-server'

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