Skip to main content
Glama

Airsockfly

Search parking

search_parking
Read-onlyIdempotent

Search airport and city parking for an entry and exit date. Prices cover every calendar day from entry to exit inclusive.

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "search_parking"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of offers to return, from 1 to 30. Default 10.
endDateYesExit date, YYYY-MM-DD.
endTimeNoExit time, HH:MM local time of the car park.
locationNoCity, airport or area of the car park. Leave empty to search everywhere.
startDateYesEntry date, YYYY-MM-DD.
startTimeNoEntry time, HH:MM local time of the car park.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, open-world search, so the safety profile is covered. The description adds genuinely new behavioral context with 'Prices cover every calendar day from entry to exit inclusive', telling the agent the returned price is a total for the whole stay rather than a per-day rate. It does not cover result ordering or pagination beyond the limit param.

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?

Two short sentences with no filler, and the core action plus the pricing scope are front-loaded. Every clause carries information the agent can act on.

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 six parameters, no output schema, and no rich annotations beyond the safety hints, the definition is only adequate: it never describes what an offer looks like (price, car park name, distance, availability) or how results are ordered. The pricing sentence partially compensates, but an agent still cannot predict the shape of the response.

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 every parameter including location, times, and limit is already documented in the schema; the baseline is 3. The description adds only the framing that entry and exit dates bound the search and price window, without clarifying time handling or what an empty location implies beyond what the schema states.

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?

The description names a specific verb (Search) and resource (airport and city parking), which cleanly separates it from siblings like search_cars or search_flights without ambiguity. It stops short of explicitly contrasting with an alternative parking-related tool, but the resource naming does the differentiating work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, no note about prerequisites (e.g. whether a location is needed for useful results), and no mention of alternatives or follow-up tools such as get_offer. At best, usage is inferred from the phrase 'Search airport and city parking'.

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