Skip to main content
Glama

İSPARK boş otoparklar

istanbul_get_parking

Retrieve live İSPARK car park availability in Istanbul, including free spaces, capacity, hours, and location, filtered by district or open status and sorted by free spaces.

Instructions

Live İSPARK car park availability in Istanbul (otopark, boş yer): free spaces, capacity, type, hours, free minutes, location. Sorted by most free spaces.

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

Input Schema

NameRequiredDescriptionDefault
ilceNoİlçe, ör. "Kadıköy", "Şişli"
limitNoEn fazla kaç kayıt döndürülsün (1–200, varsayılan 20)
sadeceAcikNoYalnız şu an açık otoparklar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; it does say the data is live and that results are sorted by most free spaces, which usefully sets result ordering expectations. However it never states that the operation is read-only, where the data comes from, how fresh it is, or what happens when no spaces are free or a district has no lots.

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?

A single dense sentence with the resource and location front-loaded, followed by the payload fields and the ordering rule. No filler, no repetition of the title, and the Turkish search synonyms earn their place for retrieval.

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?

For a simple read-only three-parameter lookup with no output schema, the description covers the domain, the returned fields, and the sort order, which is close to what an agent needs. The remaining gap is behavioral rather than structural — no note on data freshness, empty-result behavior, or how the district filter interacts with the open-only default.

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% and all three parameters (ilce, limit, sadeceAcik) are documented in the schema itself, so the baseline is 3. The description's enumeration of fields describes the response payload rather than the inputs, and adds no filtering or formatting nuance beyond the schema — notably it never connects the district filter or the open-only default to the returned set.

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 resource (İSPARK car park availability), scopes it geographically (Istanbul), and enumerates exactly what each record contains (free spaces, capacity, type, hours, free minutes, location). The parenthetical Turkish synonyms (otopark, boş yer) plus the sorting rule make it unmistakably distinct from the sibling istanbul_get_traffic_index and the other city/data tools.

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?

Usage is only implied: the word "Live" signals this is for real-time availability rather than historical or reference lookups. There is no explicit statement of when to prefer this tool, no exclusions, and no mention of any alternative for related parking questions, so an agent must infer the trigger condition.

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