Skip to main content
Glama

İl bilgileri

cografya_get_provinces

Retrieve Turkish province facts by name or plate code, including population, area, altitude, region, phone code, and coordinates; omit the query to list all 81 provinces.

Instructions

Turkish provinces (il) facts: plate code, population (nüfus), area, altitude, region, metropolitan/coastal, phone area code, coordinates. One province by name or all 81.

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

Input Schema

NameRequiredDescriptionDefault
adNoİl adı veya plaka. Boşsa 81 il.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does convey that this is a static reference-data lookup returning a fixed field set, which is useful context. It says nothing about what happens for an unknown name or plate, whether matching is case-insensitive, or how results are ordered — relevant gaps for a lookup tool with no annotation coverage.

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?

A single front-loaded sentence that begins with the resource and then lists the returned facts, with the Turkish terms in parentheses aiding disambiguation. It is dense and nearly waste-free; only the parenthetical glossary slightly pads the length.

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 one-optional-parameter reference lookup with no output schema, the description successfully substitutes for a return spec by listing the fields delivered. What remains thin — unmatched-input behavior and result ordering — is minor for this complexity, and nothing an agent needs in order to invoke it correctly 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 schema already documents the single optional 'ad' parameter including the empty-means-all-81 default. The description's 'by name' phrasing adds the name form, but omits that a plate code is also accepted (the schema's 'ad' explicitly allows plaka), leaving a small gap rather than an enrichment.

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?

States a specific resource (Turkish provinces) and enumerates the concrete facts returned: plate code, population, area, altitude, region, metropolitan/coastal flag, phone area code, coordinates. It also bounds scope with 'One province by name or all 81.' It stops short of naming the sibling it differs from (cografya_get_districts, cografya_get_neighborhoods), so an agent must infer the granularity distinction.

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?

'One province by name or all 81' implicitly tells the agent how to choose between a targeted call and a full list, which is genuine usage guidance. There is no explicit statement of when to prefer the district/neighborhood siblings, nor any prerequisite or exclusion, so the guidance is implied rather than stated.

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