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

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

iskur_health

Checks whether the İŞKUR job portal is reachable right now and reports OK, blocked, or error status with the HTTP code and probed URL.

Instructions

Check whether İŞKUR's job portal is reachable right now.

Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not run a search.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so: it enumerates the three outcome states (ok/blocked/error) with their underlying HTTP meanings, discloses that only one request is issued, and clarifies no search side effect occurs. This tells the agent exactly what a result implies and how costly the call is.

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 segments, front-loaded with the core purpose, then the return semantics, then the cost/non-side-effect note. Every clause carries information; nothing is redundant.

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?

An output schema exists, yet the description still summarizes the meaningful return fields (status, HTTP code, probed URL), which is more than required. For a zero-parameter health probe, an agent has everything needed to decide when and how to call it.

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 there is no parameter meaning to add beyond the schema baseline of 4. Nothing in the description misleads about inputs.

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?

Names a specific verb and resource ("Check whether İŞKUR's job portal is reachable right now") and explicitly distinguishes itself from the search siblings with "it does not run a search." An agent can immediately tell this is a connectivity probe, not a data-retrieval tool.

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?

The final sentence establishes scope boundaries by negating the search behavior, which routes the agent toward the search tools for actual job data. It lacks an explicit "call this before X" or "call this when errors occur" statement, so the trigger condition is implied rather than stated.

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