Skip to main content
Glama
BRO3886

Memory Custom

by BRO3886

get_current_time

Retrieve the current time to timestamp interactions and manage knowledge graph entries within the Memory Custom MCP server.

Instructions

Get the current time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.ts:55-57 (handler)
    Core handler function that executes the tool logic: returns the current time in ISO string format.
    async getCurrentTime() {
      return new Date().toISOString();
    }
  • MCP CallToolRequestSchema handler that invokes the getCurrentTime method and formats the response.
    case "get_current_time":
      return {
        content: [
          { type: "text", text: await knowledgeGraphManager.getCurrentTime() },
        ],
      };
  • index.ts:303-310 (registration)
    Tool registration in ListToolsRequestSchema, including name, description, and empty input schema.
    {
      name: "get_current_time",
      description: "Get the current time",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
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. 'Get the current time' implies a read-only operation, but it doesn't specify what time format is returned, whether it's server time or system time, if there are rate limits, or any authentication requirements. This leaves significant behavioral gaps.

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 perfectly concise at three words, front-loaded with the core action, and has zero wasted sentences. Every word earns its place by directly stating the tool's function without any fluff or redundancy.

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. However, it lacks context about the returned time format or timezone, which would be helpful for an agent to understand what to expect. Without output schema, some return value guidance is missing.

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 100% schema description coverage, so the schema already fully documents the lack of inputs. The description doesn't need to add parameter information, and it appropriately doesn't mention any. The baseline for 0 parameters is 4, as it avoids unnecessary detail.

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 tool's purpose with a specific verb ('Get') and resource ('current time'), making it immediately understandable. However, it doesn't differentiate from sibling tools, which include various CRUD operations on different resources, so it doesn't reach the highest score.

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. With sibling tools like 'read_graph' or 'search_nodes' that might involve time-related queries, there's no indication of when this simple time-fetching tool is preferred over more complex options.

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/BRO3886/mcp-memory-custom'

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