Skip to main content
Glama

Adzuna Categories

adzuna_categories
Read-onlyIdempotent

Fetch Adzuna's normalized job-category list for a country (e.g. engineering, sales, healthcare), returns tag slugs and display names. Use to enumerate valid category values before calling history or regional_stats with a category filter.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "gb"
    },
    "name": "adzuna_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYes

Output Schema

NameRequiredDescriptionDefault
resultsNo
__CLASS__No

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that the list is normalized per country and that entries carry tag slugs plus display names, which is useful context but partly duplicated by the output schema. Nothing is said about freshness, caching, or result size.

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 action and return value, then the downstream routing advice. Every clause earns its place with no filler.

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 return values needn't be re-explained, and a one-parameter lookup tool is low complexity. The description covers purpose, sequencing, and output shape adequately; the only material omission is country-code format guidance, which the schema examples partially hint at.

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 0% for the single 'country' parameter, so the description must carry the load. It says the list is scoped 'for a country', but never states the expected format (ISO-3166 alpha-2); the 'gb'/'us' hints live only in the schema examples. Net effect: the description clarifies scope but does not fully compensate for the coverage gap.

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?

Specific verb and resource: 'Fetch Adzuna's normalized job-category list for a country', with concrete examples of what categories look like (engineering, sales, healthcare) and what is returned (tag slugs and display names). It is clearly distinguishable from siblings like regional_stats and adzuna_history, which consume categories rather than enumerate them.

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?

Gives an explicit sequencing rule: 'Use to enumerate valid category values before calling history or regional_stats with a category filter.' That names the alternatives and the condition that selects them. It stops short of saying when not to use the tool (e.g., if you already know the slug), so it is not fully explicit on exclusions.

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.