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

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

iskur_list_announcements

Retrieve official İŞKUR announcements with dates, titles, and URLs, using an optional limit to return up to 10 entries.

Instructions

İŞKUR's official announcements (duyurular).

limit: 1..10 announcements returned (the site lists ~10 per page). Each announcement: date, title, 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_list_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 carries the full burden; it does disclose that the site lists roughly 10 items per page and that each result carries date, title, and url. It says nothing about authentication, rate limits, whether more pages exist beyond the limit, or whether the call is read-only.

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 compact statements — resource identity, parameter range with rationale, and returned fields — with no filler. The resource is front-loaded and the parenthetical Turkish term aids disambiguation.

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 restating returned fields is mild redundancy, but for a one-optional-parameter listing tool the definition covers identity, range, and result shape adequately. A note on whether pagination exists beyond `limit` is the only meaningful omission.

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% for the single `limit` parameter, but the description compensates fully: it gives the 1..10 range, the meaning (announcements returned), and the site's ~10-per-page context that explains the default of 10. Only the behavior at the upper bound or beyond 10 is left unaddressed.

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?

"İŞKUR's official announcements (duyurular)" names a specific resource and scope, and the sibling set (latest_jobs, search_jobs, list_cities) makes it clear this is not a job-listing tool. It stops short of an explicit verb like "list all" and doesn't contrast itself with any sibling by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what the tool returns but never states when to choose it over iskur_latest_jobs or iskur_search_jobs, nor any exclusions or prerequisites. Usage is only inferable from the content it describes.

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