Skip to main content
Glama

CyprusJobs.eu — jobs in Cyprus

Get one vacancy

get_job
Read-only

Full details of one vacancy on CyprusJobs.eu: duties, requirements, pay, town, type of work, languages, accommodation and how to apply. Pass the vacancy id or its CyprusJobs.eu link.

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": "<job>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesVacancy id or link, e.g. https://cyprusjobs.eu/jobs/waiter--abc123
languageNoLanguage of the links and labels: en, el (Greek) or ru (Russian); default en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language / description
      Added value: +"Language of the links and labels: en, el (Greek) or ru (Russian); default en"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, non-destructive lookup. The description adds useful behavioral context by enumerating the returned vacancy details (duties, pay, town, languages, accommodation, application instructions), which matters because there is no output schema. It does not describe error or not-found behavior, but the core lookup behavior is clear.

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?

Two sentences, front-loaded with the resource and return scope, with no wasted wording. The field enumeration is compact and informative.

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?

For a simple read-only single-vacancy lookup with no output schema, the description gives enough return-field context and input guidance to call it correctly. Missing only minor details such as behavior for invalid or expired vacancy links.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already explains that the job parameter accepts a vacancy id or link and that language controls link/label language. The description reinforces that either an id or a CyprusJobs.eu link is acceptable but adds no new meaning beyond the schema.

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 description clearly states this retrieves full details of a single vacancy and enumerates the fields returned, which distinguishes it from listing tools like search_jobs and vacancy_feed. It does not use an explicit verb such as 'get' or 'retrieve', but the resource and scope are unmistakable.

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: pass a vacancy id or link after finding one. The description does not explicitly say when to use this instead of search_jobs or vacancy_feed, nor does it state exclusions such as invalid or expired vacancy ids.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources