Skip to main content
Glama

search_operators

Read-onlyIdempotent

Search for tourism operators by location, service type, and price range.

Called with no parameters: returns all operators on the network.
Use latitude/longitude/radius_km for proximity search.
Results include latitude, longitude, and operator_id for each operator.
Render operators as markers on a map. Use operator_id in get_property_info and get_services.

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

Input Schema

NameRequiredDescriptionDefault
latitudeNoQuery centre latitude (WGS84), e.g. 64.15 for Reykjavík.
longitudeNoQuery centre longitude (WGS84), e.g. -21.95 for Reykjavík.
radius_kmNoSearch radius in kilometres. Recommended: 5–50 for city areas, 100+ for rural.
service_typeNoFilter by service category.
max_price_iskNoMaximum price filter in Icelandic króna, e.g. 50000 for ~350 EUR.
min_price_iskNoMinimum price filter in Icelandic króna.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely behavioral detail beyond that: an empty call returns every operator on the network (an unbounded-result warning an agent needs) and that each result carries latitude, longitude and operator_id. It stays silent on result ordering and any paging limits.

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?

Four short lines, front-loaded with the purpose, then the default behavior, then the spatial mode, then the return shape and next step. No filler and no restatement of the name.

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-value documentation is not required, and annotations cover safety, leaving the description to cover invocation modes and chaining — which it does. The remaining gap is a note on how this differs from the more specialized operator-search siblings, which matters given how many similarly named tools exist.

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?

Schema coverage is 100%, so per-parameter meaning is already handled and a 3 would be defensible. The description nevertheless adds set-level semantics the schema cannot express: what happens when all six parameters are omitted, and that the three spatial parameters are meant to be used together for proximity search.

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?

Names a specific verb and resource plus three filter axes (location, service type, price range), so the agent knows exactly what is searched. It does not differentiate itself from similarly named siblings such as search_licensed_operators or search_operators_near_itinerary, which is the only thing keeping it from a 5.

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 concrete invocation guidance: the no-parameter case returns the full network, and the latitude/longitude/radius_km trio is the proximity path. It also closes the loop downstream by telling the agent to pass operator_id to get_property_info and get_services. Missing an explicit statement of when to prefer a sibling search variant instead.

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