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

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

iskur_get_job

Retrieves full details for a single İŞKUR job listing by job number, including description, required skills, occupation, experience, education, and detail URL.

Instructions

Detail of one İŞKUR job listing.

job_no: the listing number from a search result (e.g. "00009899349"). Returns description, required skills, occupation, experience (years/months), min/max education, and the detail URL. The detail page carries no deadline or city — those come from iskur_search_jobs — and no employer name (login-gated on the site).

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": {
      "job_no": "<job_no>"
    },
    "name": "iskur_get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_noYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it warns that the detail page has no deadline, city, or employer name, and explains that employer identity is login-gated on the site. Those are exactly the gaps an agent would otherwise misreport; only rate limits or error behavior are unaddressed.

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?

The purpose and return set come first, followed by parameter meaning, then the caveats about missing fields. Every sentence adds information an agent needs; nothing is repeated from the schema or padding.

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 single-parameter detail lookup with an output schema and no annotations, this is complete: it identifies the input, its format and source, the returned fields, and the fields that are absent by design. Nothing needed 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.

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: job_no is defined as the listing number from a search result with a concrete zero-padded example ("00009899349"). That establishes both the value's origin and its format string type.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (one İŞKUR job listing) and enumerates the returned fields (description, skills, occupation, experience, education, detail URL), so an agent knows exactly what it gets. It also implicitly contrasts itself with iskur_search_jobs by noting the fields that come from search instead.

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 states that job_no is the listing number 'from a search result,' which tells the agent to call iskur_search_jobs first, and it explicitly routes the agent back to iskur_search_jobs for deadline and city. There is no explicit exclusion or negative case, but the sequencing is clear.

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