Skip to main content
Glama
Sign In

Parksy

by com.parksy.mcp
OverviewDiscussionsAdmin

Get Parking Listing

get_listing
Read-onlyIdempotent

Public details of one Parksy parking listing: title, address, prices as listed (hourly, daily, weekly, monthly), space type, features, vehicle sizes, description and the "View listing on Parksy" link where the user can contact the parking provider. Use a listing_id from search_parking or a parksy.com listing URL.

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

Input Schema

NameRequiredDescriptionDefault
urlNoA parksy.com listing URL, instead of listing_id.
listing_idNoListing id from search_parking.

Output Schema

NameRequiredDescriptionDefault
urlYes
aboutNo
titleNo
pricesNoPrices exactly as listed, keyed by period, or "Price on application".
addressNo
currencyNo
featuresNo
disclaimerNo
link_labelNo
listing_idYes
space_typeNo
descriptionNo
listing_kindNo
vehicle_sizesNo
how_to_contactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "about": {
+      "type": "string"
+    },
+    "address": {
+      "type": "string"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "features": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "how_to_contact": {
+      "type": "string"
+    },
+    "link_label": {
+      "type": "string"
+    },
+    "listing_id": {
+      "type": "integer"
+    },
+    "listing_kind": {
+      "type": "string"
+    },
+    "prices": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Prices exactly as listed, keyed by period, or \"Price on application\".",
+      "type": [
+        "object",
+        "string"
+      ]
+    },
+    "space_type": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "vehicle_sizes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "listing_id",
+    "url"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds that the data is public and that the response carries a 'View listing on Parksy' link where the user can reach the provider, which is useful behavioral context. It says nothing about failure behavior for an unknown id or about any rate limits, so the added value is moderate.

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?

A single front-loaded sentence with the resource identified first, followed by the input sourcing. The return-field enumeration is somewhat long and partly duplicates the output schema, but it helps an agent judge relevance before calling.

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 present and rich annotations, the description only needs to cover purpose, inputs and routing, all of which are present. It is slightly thin on edge cases: with zero required parameters it never states that exactly one of url or listing_id must be supplied, nor what happens when a lookup fails.

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

Parameters5/5

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

Schema coverage is 100% and both properties are documented, so the baseline would be 3. The description earns more by framing the two inputs as mutually exclusive alternatives ('listing_id ... or a parksy.com listing URL'), clarifying the either/or usage that the schema leaves implicit.

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 names a specific verb and resource ('Public details of one Parksy parking listing') and enumerates exactly what comes back (title, address, prices, space type, features, sizes, description, link). That field list plus the explicit mention of search_parking as the id source lets an agent separate this from the sibling tools without opening the schema.

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?

It tells the agent how to obtain the input ('Use a listing_id from search_parking or a parksy.com listing URL'), which is real routing guidance toward the search sibling. It does not state exclusions, e.g. that this is the wrong tool when the user has no specific listing in mind, or what to do if the listing is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Parksy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources