Skip to main content
Glama

diyanet_list_districts

Lists districts for a Turkish province by name or ID, returning Diyanet IDs, Turkish/English names, and prayer-times page URLs; optionally filter by substring and set language.

Instructions

The districts of one Turkish province, with Diyanet ids, Turkish

  • English names and the prayer-times page URL of each. province: province name ("Ankara") or id ("506"). query: optional substring filter (Turkish-insensitive). lang: "tr" (default), "en", "ar", "de" or "fr".

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": {
      "province": "<province>"
    },
    "name": "diyanet_list_districts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNotr
queryNo
provinceYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose useful behavior: the accepted province identifier formats ('Ankara' or '506'), that query is a Turkish-insensitive substring filter, and that lang defaults to tr with five allowed values. It does not explicitly state the operation is a non-mutating listing, but the wording makes that evident and an output schema exists for return values.

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?

Front-loaded with the resource and return fields, then parameter notes in compact form. Every clause carries information; only cosmetic line-wrapping and the omission of a lead-in for the parameter list keep it below a 5.

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 three-parameter read tool with a full output schema, the description covers input formats, filtering behavior, and language options adequately. An agent could call it correctly from this definition alone, with the only inferred step being that a province identifier must be obtained elsewhere.

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 and largely does: all three parameters are explained, including dual name/id input for province, substring semantics plus Turkish-insensitive matching for query, and the enumerated lang values absent from the schema's bare string type. Minor gap: it doesn't say what lang changes (presumably the language of returned names).

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 opens with a specific verb+resource: 'The districts of one Turkish province', and names the payload fields (Diyanet ids, Turkish/English names, prayer-times page URL). It is clearly distinguishable from the sibling 'diyanet_list_provinces' by resource scope, though it never names that sibling explicitly.

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?

Usage is only implied: an agent can infer this is the lookup to run after obtaining a province name or id, but the description never says so or points to diyanet_list_provinces for discovery. No exclusions or when-not-to-use conditions are given.

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