Skip to main content
Glama
io.github.mohammad-abbasi-sh/iskur-mcp

io.github.mohammad-abbasi-sh/iskur-mcp

iskur_list_cities

Lists all 81 Turkish provinces with their İŞKUR codes and names, enabling correct city selection for job searches by code or name.

Instructions

The 81 Turkish provinces İŞKUR searches by — code + name.

Use the code (e.g. "34" for İstanbul) or the name in iskur_search_jobs / iskur_latest_jobs. Parsed live from the search form; falls back to the built-in list if the form cannot be read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does disclose a non-obvious behavior: the list is parsed live from the search form with a built-in fallback if parsing fails. That provenance/reliability note is genuinely valuable. It does not mention caching or freshness/latency characteristics, which would round out the picture for a live-scraped list.

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?

Three short sentences with no filler: what the data is, how to consume it, and where it comes from. The identity of the resource is front-loaded and each sentence adds distinct information.

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?

An output schema exists, so return values need no explanation, and with zero parameters the description only needs to cover purpose, downstream use, and provenance — all of which it does. The only minor gap is guidance on name-vs-code usage details (e.g. exact spelling/characters for names).

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?

The tool takes zero parameters, so the baseline of 4 applies. The description's mention of the code format ("34" for İstanbul) is oriented toward interpreting the result rather than an input argument, but it is harmless and reinforces what the schema cannot express.

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 concrete resource and scope: the 81 Turkish provinces, each with a code and a name. The verb is only implied by the noun phrase (no explicit 'returns'/'lists'), but the scope is so specific that an agent can immediately tell this is a lookup of city codes rather than a search tool like its siblings.

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 explicitly tells the agent where the output goes: the code (e.g. "34" for İstanbul) or the name should be used in iskur_search_jobs / iskur_latest_jobs. What is left implicit is when to call this tool rather than skipping straight to search — no explicit statement that you should invoke it first when you only have an ambiguous city name.

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