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

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

iskur_search_jobs

Search Turkish İŞKUR open job listings by keyword, city, date range, work type, and education, then retrieve paginated results with job details and deadlines.

Instructions

Search İŞKUR's open job listings.

keyword: Turkish job/occupation text (e.g. "garson", "aşçı") — empty means all jobs. city: province name (e.g. "İstanbul", "Ankara") or code (e.g. "34") — empty means all provinces. date_range: "all" (default), "last_24h", "last_week", "last_15d". work_type: "all" (default), "full" (Tam Zamanlı), "part" (Kısmi Zamanlı). education: "any" (default), "illiterate", "literate", "primary", "middle", "high", "associate", "bachelor", "master", "phd". page: results page (15 jobs per page; total and page_count are returned). limit: 1..15 jobs returned. Each job: job_no, title, sector, period, work_type, open_positions, location {scope, city, district}, deadline (dd.mm.yyyy), days_left, url. The search postback is slow (~40s); prefer page 1 and narrow filters.

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_search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
pageNo
limitNo
keywordNo
educationNoany
work_typeNoall
date_rangeNoall

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?

With no annotations, the description carries the full burden and does well: it discloses that the search postback is slow (~40s), states pagination at 15 jobs per page with total and page_count returned, and enumerates the fields of each returned job. It does not cover permissions or rate limits, but the main behavioral risks (latency, paging) are surfaced.

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?

The purpose leads, followed by a compact per-parameter block and a closing performance note; nearly every clause carries information. It is dense but well-ordered, with only mild redundancy between the parameter list and the final field enumeration.

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 seven-parameter, zero-annotation, zero-schema-coverage search tool this is complete: filter vocabulary, defaults, paging model, latency expectations, and return fields are all present. The existence of an output schema makes the field listing a bonus rather than a requirement, so nothing an agent needs to call it correctly is missing.

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 description coverage is 0%, so the description must compensate and it does: every one of the seven parameters gets meaning, Turkish-language examples ("garson", "34"), default behavior for empty values, and the full allowed value sets for date_range, work_type, and education that the schema does not encode as enums. This is meaning genuinely added beyond the structured fields.

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?

Opens with a specific verb plus resource: "Search İŞKUR's open job listings." That is stronger than a restated name and lets an agent distinguish it from a record-fetch or listing tool. It stops short of naming a sibling to contrast with, so it is clear but not fully differentiated.

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 through filter semantics ("empty means all jobs", "empty means all provinces") and an operational hint to "prefer page 1 and narrow filters." There is no explicit when-to-use routing such as searching by keyword versus pulling the latest postings via a sibling, so an agent must infer the boundary.

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