Skip to main content
Glama

any.cab

Find a place in Malta

search_locations
Read-onlyIdempotent

Search hotels, addresses, towns and landmarks in Malta (Gozo and Comino are not served yet). Returns places with name, address and coordinates, in the same format a quote accepts for its from and to.

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": {
      "query": "<query>"
    },
    "name": "search_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYese.g. "Hilton St Julians", "Valletta", "Cirkewwa ferry"

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 read-only, idempotent, non-destructive, open-world search. The description adds meaningful behavior beyond that: it limits search coverage to Malta excluding Gozo and Comino, and it discloses that results include name, address and coordinates. It does not mention result limits, ranking or pagination, but the core behavior is well covered.

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?

The description is two sentences and is front-loaded with the main capability. The parenthetical geographic limitation and the quote-format compatibility note both earn their place by preventing misuse and clarifying downstream use.

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 one-parameter, read-only search tool with no output schema, the description provides the geographic scope, excluded regions, searchable entity types and returned fields. It is nearly complete, with only minor gaps around result ordering, result count and pagination behavior.

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% for the single query parameter, and the schema already includes concrete examples such as hotel, town and ferry queries. The description reinforces the categories of places that can be searched but does not add query syntax, matching rules or formatting guidance beyond the schema. With the schema carrying the parameter detail, a baseline score of 3 is appropriate.

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 states a specific verb and resource: search hotels, addresses, towns and landmarks in Malta. It also scopes coverage by excluding Gozo and Comino and describes the returned place fields. It does not explicitly differentiate itself from the sibling booking/quote tools, though the quote-format note gives useful context.

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 by the note that results are in the same format a quote accepts for its from and to, suggesting this is used to resolve places before quoting. However, the description does not explicitly say when to use this tool versus get_rates/get_quote or when another approach is required. The geographic exclusion is a coverage limit, not a full when-to-use guideline.

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