Skip to main content
Glama

weltze.it Zeitzonen

Orte suchen

search_places

Search about 6,400 cities, regions, time zone names and abbreviations; returns names, countries and IANA time zones.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch text, e.g. "san diego", "central time", "IST".
limitNoDefault 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the searchable field set, the approximate corpus size, and the exact return fields (names, countries, IANA time zones). It says nothing about match behavior (fuzzy vs exact, ranking), result ordering, or what happens on zero matches, which are the behaviors an agent would actually want to know.

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?

A single front-loaded sentence with no filler; the searchable scope comes first and the return contract follows immediately. Nothing could be cut without losing 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 two-parameter read-only lookup with no output schema and no annotations, the description covers what is searchable and what comes back, which is the essential contract. It is only slightly thin on result ordering and matching semantics, which are minor for this tool class.

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?

Schema description coverage is 100% and the schema already documents both q (with examples) and limit (default 10, max 25). The description adds no additional meaning about either parameter, so the baseline 3 applies.

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 uses a specific verb ("Search") with an enumerated resource (cities, regions, time zone names and abbreviations) and even states the corpus size (~6,400). That is enough for an agent to tell this lookup tool apart from convert_time/get_time/time_difference, but it never explicitly contrasts itself with those siblings, so it stops short of a 5.

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?

There is no explicit when-to-use or when-not-to-use statement and no mention of the sibling tools. Usage is only implied by the resource list — an agent can infer this is the lookup step before a time conversion, but the description never says so or states any exclusions.

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