Skip to main content
Glama

Casatoo

Search Casatoo locations

casatoo_search_locations
Read-onlyIdempotent

Step 1 of every location-based operation. Find candidate Casatoo location IDs by place name, slug, district, municipality, parish, or neighborhood. Inspect selection_state and location_type; ask the user when selection_required and never invent an ID.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum location candidates to return, from 1 to 25; defaults to 10.
queryYesHuman place text used only to discover candidate Casatoo location IDs. Common unambiguous English aliases such as Lisbon are accepted.

Output Schema

NameRequiredDescriptionDefault
queryYes
locationsYes
selection_stateYes
normalized_queryYes
query_interpretationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum location candidates to return, from 1 to 25; defaults to 10."
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / title
      Removed value: -"LocationSearchRequest"
  2. Changed27 schema fields changed
    • addedInput schema / $defs
      Added value: +{
      +  "LocationQuery": {
      +    "maxLength": 120,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +}
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / query / $ref
      Added value: +"#/$defs/LocationQuery"
    • addedInput schema / properties / query / description
      Added value: +"Human place text used only to discover candidate Casatoo location IDs. Common unambiguous English aliases such as Lisbon are accepted."
    • removedInput schema / properties / query / maxLength
      Removed value: -120
    • removedInput schema / properties / query / minLength
      Removed value: -1
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / query / type
      Removed value: -"string"
    • addedOutput schema / $defs / AgentLocationType
      Added value: +{
      +  "enum": [
      +    "DISTRICT",
      +    "MUNICIPALITY",
      +    "PARISH",
      +    "NEIGHBORHOOD"
      +  ],
      +  "title": "AgentLocationType",
      +  "type": "string"
      +}
    • addedOutput schema / $defs / LocationId
      Added value: +{
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / $defs / LocationQueryInterpretation
      Added value: +{
      +  "enum": [
      +    "literal",
      +    "alias"
      +  ],
      +  "title": "LocationQueryInterpretation",
      +  "type": "string"
      +}
    • addedOutput schema / $defs / LocationSearchResult / properties / id / $ref
      Added value: +"#/$defs/LocationId"
    • addedOutput schema / $defs / LocationSearchResult / properties / id / description
      Added value: +"Exact location ID to pass unchanged to listing search and search-link tools."
    • removedOutput schema / $defs / LocationSearchResult / properties / id / title
      Removed value: -"Id"
    • removedOutput schema / $defs / LocationSearchResult / properties / id / type
      Removed value: -"integer"
    • addedOutput schema / $defs / LocationSearchResult / properties / location_type / $ref
      Added value: +"#/$defs/AgentLocationType"
    • addedOutput schema / $defs / LocationSearchResult / properties / location_type / description
      Added value: +"Administrative level: DISTRICT, MUNICIPALITY, PARISH, or NEIGHBORHOOD."
    • removedOutput schema / $defs / LocationSearchResult / properties / location_type / title
      Removed value: -"Location Type"
    • removedOutput schema / $defs / LocationSearchResult / properties / location_type / type
      Removed value: -"string"
    • changedOutput schema / $defs / LocationSearchResult / properties / parent_id / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "$ref": "#/$defs/LocationId"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / $defs / LocationSearchResult / properties / parent_id / title
      Removed value: -"Parent Id"
    • addedOutput schema / $defs / LocationSelectionState
      Added value: +{
      +  "enum": [
      +    "no_candidates",
      +    "single_candidate",
      +    "selection_required"
      +  ],
      +  "title": "LocationSelectionState",
      +  "type": "string"
      +}
    • addedOutput schema / properties / normalized_query
      Added value: +{
      +  "title": "Normalized Query",
      +  "type": "string"
      +}
    • addedOutput schema / properties / query
      Added value: +{
      +  "title": "Query",
      +  "type": "string"
      +}
    • addedOutput schema / properties / query_interpretation
      Added value: +{
      +  "$ref": "#/$defs/LocationQueryInterpretation"
      +}
    • addedOutput schema / properties / selection_state
      Added value: +{
      +  "$ref": "#/$defs/LocationSelectionState"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "locations"
      -]New value: +[
      +  "query",
      +  "normalized_query",
      +  "query_interpretation",
      +  "selection_state",
      +  "locations"
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: it returns *candidate* IDs, exposes selection_state and location_type for inspection, and mandates asking the user when selection_required rather than fabricating an ID.

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?

Three compact sentences, front-loaded with the workflow role, then the lookup scope, then the safety imperatives. Every clause carries information; the final sentence packs three imperatives but none are 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?

With an output schema covering return values and annotations covering safety, the description fills the remaining gaps: where this fits in the workflow, which response fields to inspect, and how to handle a selection_required outcome. Complete enough for correct invocation.

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 baseline is 3, but the description goes further by enumerating the accepted query forms (place name, slug, district, municipality, parish, neighborhood) and noting aliases like 'Lisbon' are accepted, adding real meaning beyond the schema text.

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?

States a specific verb and resource ('Find candidate Casatoo location IDs') and prefaces it with workflow position ('Step 1 of every location-based operation'). It clearly distinguishes itself from casatoo_search_listings by targeting location IDs rather than listings.

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?

'Step 1 of every location-based operation' tells the agent exactly when this tool applies, and 'never invent an ID' plus 'ask the user when selection_required' constrain behavior at the point of use. No sibling alternative is named, but the workflow framing makes the entry point unambiguous.

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