Skip to main content
Glama

diyanet_list_provinces

Lists all 81 Turkish provinces with Diyanet IDs and names in five languages, supporting Turkish-insensitive filtering to find a province for district lookups.

Instructions

The 81 Turkish provinces with their Diyanet ids and Turkish + English names. query: optional substring filter (Turkish-insensitive, e.g. "ank" matches Ankara). lang: "tr" (default), "en", "ar", "de" or "fr". Use the id or name with diyanet_list_districts.

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

Input Schema

NameRequiredDescriptionDefault
langNotr
queryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses the useful traits: a fixed set of 81 rows, the fields returned (id plus names), and the filtering behavior (substring, Turkish-insensitive, with a worked example). It omits things like result ordering and whether filtering is applied server-side, 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?

Two compact sentences front-load the resource, then parameter semantics, then the hand-off to the sibling — good ordering with no filler. The one soft spot is the slight tension between "Turkish + English names" and a lang set that includes ar/de/fr, which reads as a leftover rather than deliberate.

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?

Low-complexity, zero-required-parameter catalog tool with an output schema, so return-value detail is legitimately omitted, and both parameters are documented. The unresolved question of what the non-tr/en lang values actually do to the returned names is the only real gap for an agent deciding whether to set `lang`.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the schema only declares bare `lang` and `query` properties — so the description must compensate, and it does: `query` is defined as an optional Turkish-insensitive substring with a concrete example, and `lang` gets a default (tr) plus its value set. Notably the allowed lang values (ar, de, fr) appear only here and not in the schema.

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 resource and scope: the 81 Turkish provinces, including their Diyanet ids and Turkish/English names. It also distinguishes itself from the sibling diyanet_list_districts by explaining that the ids/names it returns are the inputs that tool consumes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly frames this as a lookup step ("Use the id or name with diyanet_list_districts"), so the agent knows the next call in the chain. It stops short of an explicit when-to-use/when-not statement (e.g. when to call this instead of diyanet_health or diyanet_prayer_times, which likely also need a province), but the implied workflow is unambiguous.

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