Skip to main content
Glama

İlçeler

cografya_get_districts

Retrieve the districts of a Turkish province with population and area data, ordered by population so you can compare local demographics quickly.

Instructions

Districts (ilçe) of a Turkish province with population and area, most populous first.

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": {
      "il": "<il>"
    },
    "name": "cografya_get_districts"
  }
}

Input Schema

NameRequiredDescriptionDefault
ilYesİl adı veya plaka

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/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 usefully discloses the ordering ('most populous first') and the data returned (population, area), but says nothing about behavior for an unknown province name, empty results, or whether the list is complete.

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 identifying the resource, its contents, and its sort order. No redundant wording or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description covers what is returned, the unit of aggregation, and the ordering. Nothing essential for correct invocation is missing.

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 coverage is 100% and the single parameter 'il' is already documented as accepting a province name or plate code. The description only restates that the input is a province, adding no format or matching nuances beyond the schema.

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 gives a specific resource ('Districts (ilçe) of a Turkish province') with named return attributes (population, area). It implicitly contrasts with the sibling cografya_get_neighborhoods by naming the district level, but never states the distinction 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 implied: call this when you have a province and need its districts. There is no explicit guidance on when to prefer cografya_get_neighborhoods or cografya_get_provinces, and no stated prerequisites or failure conditions.

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