Skip to main content
Glama

search_licensed_operators

Read-onlyIdempotent

Search Iceland's public licensed-operator register, ranked by relevance. Results are informational registry facts, not Sóley booking inventory. Online booking through Sóley isn’t available for this operator yet. You can contact the operator directly in the meantime. For traveler follow-up, use only the listing's public website or phone. Frame results as 'licensed operator, verified contact' or 'licensed operator, public record'; 'bookable here' describes search_operators results. For completeness questions, call both tools and group the answer by capability. Based on Iceland's official operator registers. Never frame operators by membership.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum registry entries to return.
placeNoOptional postal-town filter for towns and villages like Vík or Húsavík. Diacritic- and dative-tolerant ('Vik' matches 'Vík í Mýrdal').
queryNoOptional free-text search. Matches operator and trading names AND postal towns; town matches rank first.
offsetNoNumber of matching entries to skip, for paging through a result set larger than limit. Compare total_count with offset + returned_count to tell whether more entries remain.
regionNoOptional region filter — one of Iceland's 8 landshlutar (e.g. Suðurland). A region spans many towns; for a town use place instead.
categoryNoOptional public-register category filter.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-structured context: results are informational public-register facts sourced from official registers, not booking inventory, and no online booking exists for these operators — a real limitation an agent must know before promising follow-up. It stops short of describing result volume or paging behavior, but the output schema carries the return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and scope boundary are correctly front-loaded, but the body drifts into output-phrasing boilerplate ('Frame results as...', 'Never frame operators by membership') that reads as response-style policy rather than invocation guidance. Those sentences consume roughly half the text and dilute the selection signal.

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?

With an output schema present and rich annotations, the description only needs to supply provenance, coverage limits, and sibling routing — all of which it does. The remaining gap is that the phrasing directives crowd out a brief note on result scope (e.g. register size), but nothing essential for a correct call is absent.

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 itself explains the place-vs-region distinction, diacritic tolerance, and offset/total_count paging. The description mentions no parameter at all, so it adds nothing beyond the structured fields — baseline 3 is the correct ceiling here.

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 first sentence states a specific verb and resource — search Iceland's public licensed-operator register — plus the ranking behavior (relevance). It also carves out the scope boundary versus Sóley booking inventory and names the sibling whose results mean 'bookable here' (search_operators), so an agent can separate the two tools without opening either schema.

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?

Usage is routed explicitly: use this for registry facts, use search_operators for 'bookable here', and call both when the question is about completeness. What's missing is a when-not-to-use boundary for adjacent lookups (e.g. itinerary-adjacent operator discovery), but the core this-vs-alternative decision is spelled out clearly.

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