Parksy

Parking Space Value Estimate

space_value

Read-onlyIdempotent

Estimates what a parking provider could charge for a parking space (monthly and weekly range, suggested daily and hourly price) at a place, and links to list the space on Parksy. Use this when someone asks what a garage, driveway or parking space is worth, could earn or should charge. Add the country when a place name is common. An estimate only.

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

Input Schema

Name	Required	Description	Default
`place`	No	City, suburb, neighborhood, landmark or address, for example "Surry Hills, Sydney" or "Midtown Manhattan". Add the state or country when a name is common.
`country`	No	Optional two-letter country code, for example AU, US, GB, CA, NZ or IE.
`postcode`	No	Optional postcode or ZIP code for a more local estimate.
`space_type`	No	indoor = garage or undercover, outdoor = driveway or open space.	outdoor
`secure_access`	No	Access needs a key, remote or code.

Output Schema

Name	Required	Description	Default
`note`	No
`weekly`	No
`country`	No
`message`	No
`monthly`	No
`currency`	No
`disclaimer`	No
`resolved_to`	Yes
`estimate_area`	No
`suggested_daily`	No
`suggested_hourly`	No
`list_your_space_free`	Yes
`similar_listings_nearby`	No
`other_places_with_this_name`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "country": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "currency": {
+      "type": "string"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "estimate_area": {
+      "type": "string"
+    },
+    "list_your_space_free": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "monthly": {
+      "properties": {
+        "high": {
+          "type": "string"
+        },
+        "low": {
+          "type": "string"
+        },
+        "typical": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "note": {
+      "type": "string"
+    },
+    "other_places_with_this_name": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "resolved_to": {
+      "type": "string"
+    },
+    "similar_listings_nearby": {
+      "properties": {
+        "area": {
+          "type": "string"
+        },
+        "count": {
+          "type": "integer"
+        },
+        "median_monthly": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "suggested_daily": {
+      "type": "string"
+    },
+    "suggested_hourly": {
+      "type": "string"
+    },
+    "weekly": {
+      "properties": {
+        "high": {
+          "type": "string"
+        },
+        "low": {
+          "type": "string"
+        },
+        "typical": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "resolved_to",
+    "list_your_space_free"
+  ],
+  "type": "object"
+}

First observedNov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: results are "An estimate only" (not a guarantee or quote), and the call returns links to list the space on Parksy, which an agent would not infer from annotations alone.

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?

Purpose is front-loaded in the first clause with output detail immediately after, then usage, a disambiguation tip, and a short disclaimer. Four sentences with almost no waste; the only slight redundancy is repeating the country guidance already present in the schema.

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?

All five parameters are documented in the schema, an output schema exists so return shape needn't be explained, and the description covers trigger conditions, the estimation-only caveat, and the listing-link side effect. An agent has everything needed to decide and call correctly.

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 place, country, postcode, space_type and secure_access with examples and enum meaning. The description only reinforces the country hint for common place names, adding little beyond structured data — the baseline 3 applies.

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?

States a specific verb (estimates) and resource (parking space value) plus the concrete outputs — monthly/weekly range, suggested daily and hourly price — and notes it returns links to list on Parksy. This is far more specific than a title restatement, though it never names a sibling tool to contrast with, so it stops just short of a 5.

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?

"Use this when someone asks what a garage, driveway or parking space is worth, could earn or should charge" gives a clear trigger condition with concrete user phrasings. No when-not-to-use or alternative-tool routing is provided (e.g. versus search_parking or parking_guides), which keeps it from a 5.

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

All Parksy tools Inspect

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

Need Help?