Skip to main content
Glama

WhatsMood

List cities with upcoming events

list_cities
Read-onlyIdempotent

List cities that currently have upcoming events on WhatsMood (most events first) with their city page URL. TR: Etkinliği olan şehirler.

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": "list_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO country code filter, e.g. TR, GB, DE, or ALL (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that results are ordered by most events first and include each city's page URL. It also clarifies the temporal scope as currently upcoming events. Pagination and result limits are not described, which keeps it from a 5.

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 description is a single front-loaded sentence that quickly conveys the core behavior, ordering, and return field. The appended Turkish translation is redundant for most agents, preventing a perfect conciseness score.

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 read-only list tool with one optional filter, the description covers the essential purpose, ordering, and a key return field. Pagination behavior and exact result structure are not stated, but the annotations and schema carry most remaining context.

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 single country parameter is fully documented there, including ISO examples and the ALL default. The description adds no additional parameter meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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: list cities that currently have upcoming events on WhatsMood. It also adds sort order and return content, making the purpose clear. It does not explicitly distinguish this tool from siblings such as search_events or find_nearby_places, so it falls 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?

The use case is implied by 'cities that currently have upcoming events,' but the description gives no explicit when-to-use guidance, exclusions, or named alternatives. An agent can infer the basic purpose but receives no routing help relative to sibling tools.

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