Skip to main content
Glama

InterfaceDelta canary (test server)

Current time

get_time
Read-only

Returns the current time in UTC, or in an IANA time zone if given. Test tool from InterfaceDelta.

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
timezoneNoIANA time zone, e.g. Europe/Berlin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe read-only, non-destructive, closed-world operation, so the bar is lower; the description still adds real behavioral content by naming the default (UTC) and the conversion branch when a zone is supplied. It stops short of saying what the returned value looks like or what happens with an invalid zone identifier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The behavioral sentence is front-loaded and wastes no words. The trailing 'Test tool from InterfaceDelta' is origin metadata that does not help an agent decide or invoke, so it dilutes rather than earns its place.

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 zero-required-parameter utility with full schema coverage and complete annotations, this is nearly sufficient. The only gap is the return value's format, which matters because no output schema exists to describe it.

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?

Schema coverage is 100% and the single parameter is already documented with an example, so the baseline is 3. The description slightly exceeds that by making the parameter's optionality and default meaningful ('or in an IANA time zone if given'), which the schema alone does not state.

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?

States a specific verb and resource ('Returns the current time') plus the scope ('in UTC, or in an IANA time zone if given'), so the agent knows exactly what it gets. Nothing about it could be confused with the arithmetic or echo siblings.

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?

Usage is only implied: the agent can infer it should call this when it needs the present moment, and that supplying a time zone yields local time instead of UTC. There is no explicit when-to-use, when-not-to-use, or named alternative, though for a single-purpose utility there is little to disambiguate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources