Skip to main content
Glama

Cayman Job Finder

Cayman Hiring Report figures

hiring_report_stats
Read-onlyIdempotent

Headline figures from the published monthly Cayman Hiring Report (job adverts posted on the official WORC Jobs Portal that month: adverts, positions, employers, median advertised pay, most advertised sectors, best-paid sectors, advert length), exactly as published, with a link to the full report and its method. These are counts of public adverts by Cayman Job Finder, not official WORC statistics. Defaults to the latest edition.

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": "hiring_report_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
editionNoReport month as YYYY-MM (published: 2026-10). Default: the latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the added value is provenance and caveats: 'exactly as published', the link to the full report and method, and the warning that these are Cayman Job Finder counts of public adverts rather than official WORC statistics. That is genuinely non-obvious context an agent would otherwise misattribute. Return-format details are the only gap.

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?

The core purpose is front-loaded and the provenance caveat closes the text, but the middle is one very long parenthetical list that strains readability. Nearly every clause carries information the agent needs (especially the field list, since there is no output schema), so the density is justified, if inelegant.

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?

With no output schema, the description compensates by enumerating what the response contains (adverts, positions, employers, median pay, sectors, advert length) plus the link to the full report and method. Combined with annotations covering safety, an agent has everything needed to call this correctly and interpret the result.

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?

The single `edition` parameter is fully documented in the schema (100% coverage, enum, default stated), and the description's 'Defaults to the latest edition' merely restates it. The description adds no format or edition-availability detail beyond the schema, so this sits at the baseline.

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 a specific resource (headline figures from the published monthly Cayman Hiring Report) and enumerates the exact measures returned: adverts, positions, employers, median advertised pay, sectors, advert length. That scope is unmistakably distinct from the sibling tools get_job, list_employers and search_jobs, which operate on individual records.

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 gives clear context for when the tool applies – aggregate/headline figures rather than individual adverts – and states the default behaviour (latest edition), which is the main invocation decision here. It stops short of explicitly naming when not to use it or pointing at a sibling for per-advert lookups.

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.