Skip to main content
Glama

Casatoo

Build a public Casatoo search link

casatoo_build_search_link
Read-onlyIdempotent

Create a public Casatoo URL for an exact location_id returned by casatoo_search_locations. This is a strict two-step flow: never pass place text or invent an ID. Include only filters the user provided; do not guess missing criteria.

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": {
      "location_id": "<location_id>"
    },
    "name": "casatoo_build_search_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomsNoPortuguese bedroom typologies. T2 means two bedrooms and T5+ matches Casatoo listings with five or more bedrooms. An empty list means any room count.
sort_byNoSearch-link ordering; defaults explicitly to newest.newest
price_maxNoMaximum asking price in EUR, inclusive; e.g. 500000. Omit for no maximum.
price_minNoMinimum asking price in EUR, inclusive; e.g. 200000. Omit for no minimum.
location_idYesExact Casatoo location ID returned by casatoo_search_locations. Free-text locations are not accepted.
gross_area_maxNoMaximum gross floor area in square metres, inclusive; e.g. 150. Omit for no maximum.
gross_area_minNoMinimum gross floor area in square metres, inclusive; e.g. 80. Omit for no minimum.
property_categoryNoOptional property category, e.g. apartment or house; omit for any category.

Output Schema

NameRequiredDescriptionDefault
urlYes
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • removedInput schema / $defs / PropertyCategory / title
      Removed value: -"PropertyCategory"
    • removedInput schema / $defs / SearchSort / title
      Removed value: -"SearchSort"
    • addedInput schema / properties / gross_area_max / description
      Added value: +"Maximum gross floor area in square metres, inclusive; e.g. 150. Omit for no maximum."
    • removedInput schema / properties / gross_area_max / title
      Removed value: -"Gross Area Max"
    • addedInput schema / properties / gross_area_min / description
      Added value: +"Minimum gross floor area in square metres, inclusive; e.g. 80. Omit for no minimum."
    • removedInput schema / properties / gross_area_min / title
      Removed value: -"Gross Area Min"
    • addedInput schema / properties / price_max / description
      Added value: +"Maximum asking price in EUR, inclusive; e.g. 500000. Omit for no maximum."
    • removedInput schema / properties / price_max / title
      Removed value: -"Price Max"
    • addedInput schema / properties / price_min / description
      Added value: +"Minimum asking price in EUR, inclusive; e.g. 200000. Omit for no minimum."
    • removedInput schema / properties / price_min / title
      Removed value: -"Price Min"
    • addedInput schema / properties / property_category / description
      Added value: +"Optional property category, e.g. apartment or house; omit for any category."
    • removedInput schema / properties / rooms / title
      Removed value: -"Rooms"
    • removedInput schema / title
      Removed value: -"AgentSearchLinkRequest"
  2. Changed23 schema fields changed
    • addedInput schema / $defs / LocationId
      Added value: +{
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / location
      Removed value: -{
      -  "maxLength": 120,
      -  "minLength": 1,
      -  "title": "Location",
      -  "type": "string"
      -}
    • addedInput schema / properties / location_id
      Added value: +{
      +  "$ref": "#/$defs/LocationId",
      +  "description": "Exact Casatoo location ID returned by casatoo_search_locations. Free-text locations are not accepted."
      +}
    • addedInput schema / properties / rooms / description
      Added value: +"Portuguese bedroom typologies. T2 means two bedrooms and T5+ matches Casatoo listings with five or more bedrooms. An empty list means any room count."
    • addedInput schema / properties / rooms / maxItems
      Added value: +6
    • addedInput schema / properties / sort_by / $ref
      Added value: +"#/$defs/SearchSort"
    • removedInput schema / properties / sort_by / anyOf
      Removed value: -[
      -  {
      -    "$ref": "#/$defs/SearchSort"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sort_by / default
      Previous value: -nullNew value: +"newest"
    • addedInput schema / properties / sort_by / description
      Added value: +"Search-link ordering; defaults explicitly to newest."
    • changedInput schema / required
      Previous value: -[
      -  "location"
      -]New value: +[
      +  "location_id"
      +]
    • 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 / 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"
  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 establish read-only, idempotent, non-destructive behavior, so the description does not need to restate safety basics. It adds useful behavioral constraints beyond annotations: the required two-step flow, the ban on free-text or invented IDs, and the rule not to infer missing filters.

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 three tightly written sentences with the purpose front-loaded and the key constraints immediately following. Every sentence adds operational value, and there is no redundant restatement of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema, output schema, and read-only annotations, the description supplies what is missing for correct invocation: the prerequisite location lookup and the rule against inventing IDs or guessing filters. An agent has enough information to call this tool correctly without needing return-value details in the description.

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%, so the schema already documents all parameters in detail. The description reinforces the provenance and exactness of location_id, but it does not add syntax or meaning for the other seven filters beyond the general instruction to include only user-provided criteria.

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 description uses a specific verb and resource: create a public Casatoo URL for a search link. It also makes clear that the link is built from an exact location_id returned by casatoo_search_locations, which distinguishes it from sibling tools that search or retrieve 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?

The description gives clear usage context by declaring a strict two-step flow and prohibiting free-text places or invented IDs. It also says to include only filters the user provided and not guess missing criteria, though it does not explicitly name alternatives such as using casatoo_search_listings for direct search results.

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