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

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

iskur_latest_jobs

Fetches İŞKUR job postings from the past 24 hours, with optional province filtering, and returns titles, sectors, deadlines, and application URLs.

Instructions

Jobs posted on İŞKUR in the last 24 hours.

city: province name (e.g. "İstanbul") or code (e.g. "34") — empty means all provinces. limit: 1..15 jobs returned. Each job: job_no, title, sector, period, work_type, open_positions, location {scope, city, district}, deadline, days_left, url.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 and does disclose the key constraints: a hard 24-hour recency window and a capped result size of 1..15. It says nothing about authentication, rate limits, pagination, or whether an empty result is normal, which leaves meaningful behavioral gaps for an unannotated tool.

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?

It is compact and front-loaded, leading with the scope before parameter definitions. The trailing enumeration of returned job fields duplicates what the output schema already provides, which is the one element that does not fully earn its space.

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?

Both parameters are fully explained despite zero schema coverage, the recency and size constraints are stated, and an output schema exists so return values need no further description. For a simple two-parameter listing tool, nothing an agent needs in order to call it is missing.

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 coverage is 0%, so the description must compensate, and it largely does: city accepts a province name ("İstanbul") or numeric code ("34") with empty meaning all provinces, and limit is bounded to 1..15. This is exactly the meaning the bare schema lacks; only the default of 15 is left unstated.

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 opening sentence states a specific verb-like scope (jobs posted) plus a precise temporal filter (last 24 hours) and the source (İŞKUR), which functionally separates it from the sibling iskur_search_jobs. It stops short of naming that alternative explicitly, so it is clear but not maximally differentiating.

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: the 24-hour window signals 'use this for recent postings', and 'empty means all provinces' clarifies the default behavior of city. There is no explicit when-to-use/when-not guidance pointing to iskur_search_jobs for keyword or historical queries.

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