Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ptv_departures

Retrieve upcoming PTV departures for a specified stop, with optional route, direction, and transport-type filters to check train, tram, bus, V/Line, or night service times.

Instructions

Get PTV departures for a stop. In full UnClick, stop_id can be filled from saved Memory defaults.

Input Schema

NameRequiredDescriptionDefault
api_keyNo
stop_idNoPTV stop ID. Optional when a saved UnClick Memory default exists.
route_idNo
route_typeNo0=train, 1=tram, 2=bus, 3=vline, 4=night. Defaults to train.
max_resultsNoDefaults to 5, maximum 20.
direction_idNo
look_backwardsNo
include_cancelledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.11
    • addedInput schema / properties / direction_id
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / properties / include_cancelled
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / look_backwards
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / max_results / description
      Added value: +"Defaults to 5, maximum 20."
    • changedInput schema / properties / route_type / description
      Previous value: -"0=train,1=tram,2=bus,3=vline,4=night"New value: +"0=train, 1=tram, 2=bus, 3=vline, 4=night. Defaults to train."
    • addedInput schema / properties / stop_id / description
      Added value: +"PTV stop ID. Optional when a saved UnClick Memory default exists."
    • removedInput schema / required
      Removed value: -[
-  "route_type",
-  "stop_id"
-]
  2. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the Memory-default behavior but omits rate limits, auth requirements (PTV keys are typically rate-limited), and whether results are real-time vs scheduled. For a data-fetch tool with zero annotations, this is thin.

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?

Two short sentences, front-loaded with the core action, no padding. Efficient for what little it conveys, though the brevity contributes to the gaps elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Eight parameters, no annotations, no output schema, and 38% schema coverage – the description does almost nothing to close the gap. Missing: what departures look like (time, route, direction), whether real-time or timetable, and semantics of the many boolean/numeric filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 38% with 8 parameters. The description only adds meaning for stop_id (Memory default) – route_id, direction_id, look_backwards, and include_cancelled are entirely undocumented in both schema and description. That is a significant gap the description should help close but does not.

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 ('Get') and resource ('PTV departures for a stop'), which is clear enough to distinguish it from ptv_disruptions, ptv_route_directions, and ptv_search. It does not explicitly name those siblings, so it misses the top of the scale but the resource is concrete.

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 when-to-use versus when-not-to-use guidance, and no mention of the sibling tools (ptv_disruptions, ptv_route_directions, ptv_search, ptv_stops_on_route). The only usage hint is the Memory-default note, which is about parameter filling, not tool selection.

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