Skip to main content
Glama

Parking Guides

parking_guides
Read-onlyIdempotent

Search Parksy parking guides and articles: free and cheap parking, parking rates, fines and appeals, towing, disability parking, permits, signs, street rules, car storage and moving day, for a city or suburb or in general. Returns titles, short summaries, last-updated dates and links. Use this when a driver asks what to do or what the rules are (towed, clamped, fined, permits, signs). Details such as the city are optional.

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": {
      "query": "<query>"
    },
    "name": "parking_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
placeNoOptional city or suburb name, for example "Brighton".
queryYesWhat the person wants to know, in a few words.
topicNoany
countryNoOptional two-letter country code, for example AU, US, GB, CA, NZ or IE.

Output Schema

NameRequiredDescriptionDefault
guidesYes
disclaimerNo
no_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "guides": {
      +      "items": {
      +        "properties": {
      +          "last_updated": {
      +            "type": "string"
      +          },
      +          "place": {
      +            "type": "string"
      +          },
      +          "summary": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "no_results": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "guides"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds that results include titles, summaries, last-updated dates and links, plus that location details are optional, but since an output schema exists this is largely redundant and no rate limits or ranking behavior are disclosed.

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?

The purpose and topic list are front-loaded and the usage sentence follows logically. The long comma-separated topic enumeration is dense but each item maps to real coverage; only the return-fields sentence is arguably wasted given the output schema.

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 read-only search tool with an output schema and mostly documented parameters, the description supplies enough to call it correctly: what it searches, when to use it, and that location is optional. Minor gaps around limit and country semantics are the only shortfall.

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 coverage is 60%, and the description clarifies that the city/place is optional and that the query is a short natural-language question, which maps to the topic enum list. It says nothing about limit or country, leaving part of the parameter set to the schema alone, so this sits at the baseline.

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?

Opens with a specific verb and resource ('Search Parksy parking guides and articles') and enumerates the covered topics, which implicitly separates it from siblings like search_parking (spaces) or fine_appeal_check. It never names an alternative explicitly, so differentiation is inferred rather than stated.

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?

Gives a clear triggering condition: 'Use this when a driver asks what to do or what the rules are (towed, clamped, fined, permits, signs).' That is concrete context for selection, but there is no when-not guidance and no named alternative for overlapping cases such as fine appeals.

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