Skip to main content
Glama
dragosh29

AppyWay MCP server

by dragosh29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get a zone and its default rules

get_zone_rules
Read-onlyIdempotent

Retrieve a controlled parking zone by ID with its type, notes and default kerb-type rules over a time window, showing when each applies and the maximum stay; bay rules override.

Instructions

One zone (e.g. a controlled parking zone) by id with its type, notes and the default rules that apply to its kerb types over a time window: when each default (single yellow line, paid bay, ...) is in force and the maximum stay. Rules set on an individual bay override these defaults.

Input Schema

NameRequiredDescriptionDefault
zone_idYesZone id (zone_id from find_parking_rules_near, fetch_kerb_segments or get_parking_entity)
end_timeNoEnd of the window; defaults to 24 hours after start_time
start_timeNoStart of the window; defaults to now
include_contact_detailsNoReturn telephone numbers of payment providers, car park operators and notes, and stop redacting email addresses and phone numbers from names, notes, tags, addresses and location codes
on_street_parking_typesNoOnly these kerb types (default: every type the zone defines a default for)
include_not_applicable_timesNoAlso list the windows in which each default does not apply

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds useful domain behavior — defaults are per kerb type with in-force windows and a max stay, and bay-level rules take precedence — but says nothing about result size, pagination, or failure modes.

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 compact sentence front-loaded with the resource and its identity key. The parenthetical examples ('single yellow line, paid bay, ...') cost a little space but usefully anchor an unfamiliar domain.

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 no output schema, the description usefully enumerates the payload shape (type, notes, per-kerb-type defaults, in-force windows, max stay). For a 6-parameter read tool that mostly does what its name says, this is close to sufficient; only result volume and error behavior are unaddressed.

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 (zone_id, start_time, end_time, include_contact_details, on_street_parking_types, include_not_applicable_times) is already documented in the schema. The description reinforces the notion of a time window and kerb-type scope but adds no syntax, format, or defaulting information beyond that.

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?

States a specific verb and resource ('One zone ... by id with its type, notes and the default rules'), scoping exactly what is returned. It is clearly distinguishable from siblings like find_parking_rules_near (search) and fetch_kerb_segments (segment geometry), which operate at a different granularity.

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 implied by the id-based lookup phrasing, and the closing note that 'Rules set on an individual bay override these defaults' implicitly tells the agent when zone-level defaults are insufficient. However, no sibling tool is named as an alternative and there are no explicit when-not conditions.

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

Deploy Server

Other Tools