astrbot-mcp

get_time

Retrieves the current local time for a specified IANA timezone, such as Asia/Shanghai or UTC, so agents can answer time-sensitive queries accurately.

Instructions

获取指定时区的当前时间。

Args: timezone: IANA 时区名，例如 Asia/Shanghai、UTC、America/New_York。

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

Name	Required	Description	Default
`timezone`	No		Asia/Shanghai

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A4/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 behavioral burden. The word 'get' and 'current time' imply a read-only operation, but the description does not explicitly state that it has no side effects, whether it requires permissions, or how invalid timezones are handled.

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 short, front-loaded, and contains no unnecessary text. The parameter note is compact and directly useful.

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?

The tool has one optional parameter and an output schema, so return values need not be explained. The description covers the parameter semantics well, though it does not explicitly mention the default timezone behavior when the parameter is omitted, which is only visible in the schema.

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 description coverage is 0%, so the description must compensate. It does so by explaining that the timezone parameter expects an IANA timezone name and giving concrete examples such as Asia/Shanghai, UTC, and America/New_York.

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 and resource: retrieving the current time in a specified timezone. It is unambiguous and not confusable with any sibling tool such as get_weather or convert_currency.

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 when to use the tool by stating its function, but it does not explicitly name alternatives, exclusions, or prerequisites. For a simple utility this is adequate but minimal.

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