Skip to main content
Glama

Search Parking Spaces

search_parking
Read-onlyIdempotent

Find parking spaces, garages, driveways and car parks listed on Parksy near a place. Returns up to 10 listings with type, price as listed, distance, features and a "View listing on Parksy" link. For daily, monthly or hourly parking. Parksy does not take bookings: people contact the parking provider on Parksy.

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

Input Schema

NameRequiredDescriptionDefault
sortNodistance
limitNo
placeNoCity, suburb, neighborhood, landmark or address, for example "Surry Hills, Sydney" or "Midtown Manhattan". Add the state or country when a name is common.
countryNoOptional two-letter country code, for example AU, US, GB, CA, NZ or IE.
featuresNoOnly listings with all of these features.
radius_kmNoSearch radius in km (max 25). Default 3.
space_typeNoany

Output Schema

NameRequiredDescriptionDefault
noteNo
aboutNo
countryNo
resultsYes
radius_kmYes
wanted_adNo
disclaimerNo
no_resultsNo
resolved_toYes
widened_from_kmNo
more_results_urlNo
nearest_listingsNo
other_places_with_this_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "about": {
      +      "type": "string"
      +    },
      +    "country": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "more_results_url": {
      +      "type": "string"
      +    },
      +    "nearest_listings": {
      +      "properties": {
      +        "area": {
      +          "type": "string"
      +        },
      +        "distance": {
      +          "type": "string"
      +        },
      +        "link_label": {
      +          "type": "string"
      +        },
      +        "parking_page_url": {
      +          "type": "string"
      +        },
      +        "search_url": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "no_results": {
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "other_places_with_this_name": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "radius_km": {
      +      "type": "number"
      +    },
      +    "resolved_to": {
      +      "type": "string"
      +    },
      +    "results": {
      +      "items": {
      +        "properties": {
      +          "area": {
      +            "type": "string"
      +          },
      +          "currency": {
      +            "type": "string"
      +          },
      +          "distance": {
      +            "type": "string"
      +          },
      +          "features": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "link_label": {
      +            "type": "string"
      +          },
      +          "listing_id": {
      +            "type": "integer"
      +          },
      +          "prices": {
      +            "additionalProperties": {
      +              "type": "string"
      +            },
      +            "description": "Prices exactly as listed, keyed by period, or \"Price on application\".",
      +            "type": [
      +              "object",
      +              "string"
      +            ]
      +          },
      +          "space_type": {
      +            "type": "string"
      +          },
      +          "summary": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "listing_id",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "wanted_ad": {
      +      "properties": {
      +        "how": {
      +          "type": "string"
      +        },
      +        "link_label": {
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "widened_from_km": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "resolved_to",
      +    "radius_km",
      +    "results"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: results are capped at 10 listings with named fields and a link, price is "as listed", and Parksy does not take bookings so users must contact the provider — an important limitation for the agent to relay.

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 short sentences, front-loaded with the core action and results, then the usage note and the booking caveat. Nothing is padded, though the fragment "For daily, monthly or hourly parking" sits awkwardly between two fuller sentences.

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

Completeness3/5

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

With an output schema present, the return values do not need explaining, and annotations carry the safety profile, so the bar is lower. Still, for a 7-parameter search tool the definition leaves the agent guessing about how sort, features and space_type shape results, which is a real gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 57%; sort, limit and space_type have no descriptions at all, and the description does not compensate by explaining ranking options or the meaning of the space types. Its only concrete contribution is the implicit "near a place" mapping to the place parameter and the "up to 10" cap that matches limit's maximum.

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?

A specific verb plus resource ("Find parking spaces, garages, driveways and car parks ... near a place") tells an agent exactly what the tool returns, including the scope of listing types. It never references the sibling tools (parking_guides, space_value, get_listing), so the differentiation work is left to the names alone.

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?

"For daily, monthly or hourly parking" gives a loose usage context, and the no-bookings note heads off a common wrong expectation. There is no explicit when-to-use or when-not-to-use guidance, and no routing toward parking_guides or space_value for adjacent questions.

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