Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

date-timeZone

Returns a random IANA time zone name to supply realistic time zone data for tests, demos, and date/time handling scenarios.

Instructions

Returns a random IANA time zone name.

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": "date-timeZone"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/5.0
Behavior3/5

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

Because no annotations are provided, the description carries the full burden of disclosing behavior. It does disclose the most important trait: the return value is random, not a fixed or parameterized zone. However, it does not say whether each call yields a different value, how large the sampling pool is, or that there is no authentication or side effect.

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 sentence with no filler, and it leads with the return value. Every word serves a purpose, and the randomness trait is stated up front.

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?

For a zero-parameter tool with no output schema and no annotations, the description is close to sufficient because the return type and the randomness are stated. However, it omits any disambiguation from the sibling location-timeZone, which is the one real risk of misuse for an agent choosing among date tools.

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 takes zero parameters, and the schema is an empty object, so there is nothing for the description to clarify. The baseline score for a zero-parameter tool applies. The description does not misdescribe any input.

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 states a specific verb and resource: it returns an IANA time zone name, and it notes that the value is random. An agent can understand what the tool produces. However, it does not distinguish this tool from the sibling location-timeZone, which apparently provides a time zone for a location; this description does not say how the two differ.

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 gives no guidance on when to use this tool rather than the sibling location-timeZone or the other date-* tools. It also does not say whether the tool is for test data, fixtures, or general use, so the agent must infer the appropriate context.

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