Skip to main content
Glama
Sign In
ChillMCP

ChillMCP

by DreamFriend011020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Get Current Time

get-time

Retrieve the current timestamp and timezone information. Select ISO, Unix, or locale format to match your requirement.

Instructions

Returns the current timestamp and timezone information

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-time"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoTime format (default: iso)

Output Schema

NameRequiredDescriptionDefault
formatYes
timezoneYes
timestampYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/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. It clearly indicates a read-only retrieval operation via 'returns', but it does not disclose behavioral details such as whether the time is UTC or local, how timezone information is represented, or any limitations. This is adequate but not rich.

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 filler. It front-loads the core behavior and avoids repeating schema or sibling information.

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?

For a simple tool with one optional parameter, an existing output schema, and a clear purpose, the description is mostly complete. It could add a note about timezone semantics or default behavior, but nothing essential is missing for an agent to invoke it correctly.

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

Parameters3/5

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

The schema covers 100% of the single parameter, including an enum and a description of the default format. The tool description adds little beyond the schema, so a baseline score of 3 is appropriate.

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 states a specific verb ('returns') and a clear resource ('current timestamp and timezone information'), which makes the tool's purpose immediately obvious. It is easily distinguished from the sibling tools (echo, add, multiply, calculate), which all perform different operations.

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 the tool should be used when the current time or timezone is needed, but it does not explicitly state when to choose this over alternatives or provide exclusions. Sibling names make alternatives obvious enough, but there is no direct routing guidance.

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