← WebMCP Directory

Tool tree

gildongmu.dodoplanet.space

Travel & EventsTools verified
Website
Gildongmu
Explore capabilities

    page: Every page

    describe_appAnswer

    Describe what the Gildongmu app can do for an agent: the tools, which are available in this deployment, how they chain (search_places → get_place_info / plan_directions → route detail), and the station info axes. Call once at the start.

    View tool JSON
    {
      "name": "describe_app",
      "kind": "answer",
      "impl": "imperative",
      "description": "Describe what the Gildongmu app can do for an agent: the tools, which are available in this deployment, how they chain (search_places → get_place_info / plan_directions → route detail), and the station info axes. Call once at the start.",
      "inputSchema": {
        "type": "object",
        "properties": {},
        "additionalProperties": false
      },
      "page": "/en"
    }
    search_placesAction

    Search places and addresses in Korea by name, address or keyword, exactly as the app's search box does. Returns places (with a ref to pass to get_place_info or plan_directions.toRef), addresses, and web results when nothing local matched. The app moves to the home screen and shows the same results.

    View tool JSON
    {
      "name": "search_places",
      "kind": "act",
      "impl": "imperative",
      "description": "Search places and addresses in Korea by name, address or keyword, exactly as the app's search box does. Returns places (with a ref to pass to get_place_info or plan_directions.toRef), addresses, and web results when nothing local matched. The app moves to the home screen and shows the same results.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "query": {
            "type": "string",
            "description": "Place name, address, or keyword, e.g. '강남역' or 'Seoul Station'."
          },
          "sort": {
            "type": "string",
            "enum": [
              "accuracy",
              "review"
            ],
            "description": "accuracy (default) or review (Naver review order, Korean only)."
          }
        },
        "required": [
          "query"
        ],
        "additionalProperties": false
      },
      "page": "/en"
    }
    get_place_infoAction

    Open a place from search_places by ref and return its info exactly as shown: category, addresses, phone; for stations the timetable (first/last trains), accessibility facilities, real-time arrivals; and barrier-free facilities. Pick axes to narrow. If truncated, call again with one axis and offset. refresh re-fetches. The app moves to the place screen.

    View tool JSON
    {
      "name": "get_place_info",
      "kind": "act",
      "impl": "imperative",
      "description": "Open a place from search_places by ref and return its info exactly as shown: category, addresses, phone; for stations the timetable (first/last trains), accessibility facilities, real-time arrivals; and barrier-free facilities. Pick axes to narrow. If truncated, call again with one axis and offset. refresh re-fetches. The app moves to the place screen.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "ref": {
            "type": "string",
            "description": "A place or address ref from search_places."
          },
          "axes": {
            "type": "array",
            "items": {
              "type": "string",
              "enum": [
                "basic",
                "timetable",
                "facilities",
                "arrivals",
                "barrierFree"
              ]
            },
            "description": "Which info to return. Omit for all that apply (non-stations: basic, barrierFree)."
          },
          "refresh": {
            "type": "boolean",
            "description": "Re-fetch the requested axes (real-time arrivals etc.)."
          },
          "offset": {
            "type": "integer",
            "minimum": 0,
            "description": "Item offset for paging one axis (requires exactly one axis in axes)."
          }
        },
        "required": [
          "ref"
        ],
        "additionalProperties": false
      },
      "page": "/en"
    }
    plan_directionsAction

    Plan a trip: resolve the destination (to, or toRef from search_places), optional origin and one via point, run the search for transit, walking and driving as the user would, and return a summary per mode with a planId and route keys. Walking returns its lines as shown on screen (Korean: shortest, then main-road and step-free only if different). Origin defaults to the user's current location, which stays in the browser. Ambiguous names return candidates. The app moves to the directions screen.

    View tool JSON
    {
      "name": "plan_directions",
      "kind": "act",
      "impl": "imperative",
      "description": "Plan a trip: resolve the destination (to, or toRef from search_places), optional origin and one via point, run the search for transit, walking and driving as the user would, and return a summary per mode with a planId and route keys. Walking returns its lines as shown on screen (Korean: shortest, then main-road and step-free only if different). Origin defaults to the user's current location, which stays in the browser. Ambiguous names return candidates. The app moves to the directions screen.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "to": {
            "type": "string",
            "description": "Destination: a place name or address, e.g. 'Seoul Station' or '세종대로 110'. Exclusive with toRef."
          },
          "toRef": {
            "type": "string",
            "description": "Destination as a ref from search_places (no text lookup). Exclusive with to."
          },
          "toCandidateId": {
            "type": "string",
            "description": "Pick one of the candidates returned by needsDisambiguation."
          },
          "from": {
            "type": "string",
            "description": "Origin place name or address. Omit for the user's current location."
          },
          "fromCandidateId": {
            "type": "string"
          },
          "via": {
            "type": "string",
            "description": "One via point. Transit does not support via and reports unsupportedWaypoint."
          },
          "viaCandidateId": {
            "type": "string"
          }
        },
        "additionalProperties": false
      },
      "page": "/en"
    }
    get_transit_route_detailAnswer

    Return one transit route from the current plan in full: every leg with line, boarding and alighting stops, station count, walking distance, and the quick-exit door (which car and door to board so you alight next to the elevator or the transfer passage). Requires planId and routeKey from plan_directions.

    View tool JSON
    {
      "name": "get_transit_route_detail",
      "kind": "answer",
      "impl": "imperative",
      "description": "Return one transit route from the current plan in full: every leg with line, boarding and alighting stops, station count, walking distance, and the quick-exit door (which car and door to board so you alight next to the elevator or the transfer passage). Requires planId and routeKey from plan_directions.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "planId": {
            "type": "string",
            "description": "planId from plan_directions."
          },
          "routeKey": {
            "type": "string",
            "description": "routeKey from plan_directions."
          }
        },
        "required": [
          "planId",
          "routeKey"
        ],
        "additionalProperties": false
      },
      "page": "/en"
    }
    get_route_stepsAnswer

    Return walking or driving directions from the current plan as a numbered page of step sentences, exactly as shown on screen. Page with offset and limit. For walking, variant picks one of the plan's walk lines by kind (default: the first line). Requires planId.

    View tool JSON
    {
      "name": "get_route_steps",
      "kind": "answer",
      "impl": "imperative",
      "description": "Return walking or driving directions from the current plan as a numbered page of step sentences, exactly as shown on screen. Page with offset and limit. For walking, variant picks one of the plan's walk lines by kind (default: the first line). Requires planId.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "planId": {
            "type": "string",
            "description": "planId from plan_directions."
          },
          "mode": {
            "type": "string",
            "enum": [
              "walk",
              "car"
            ],
            "description": "Which directions to page."
          },
          "variant": {
            "type": "string",
            "enum": [
              "shortest",
              "accessible",
              "broad",
              "recommended"
            ],
            "description": "walk only: a walk line kind from plan_directions (accessible = avoiding stairs, broad = main-road). Default: the first line."
          },
          "offset": {
            "type": "integer",
            "minimum": 0,
            "description": "0-based start index. Default 0."
          },
          "limit": {
            "type": "integer",
            "minimum": 1,
            "maximum": 20,
            "description": "Steps per page, 1 to 20. Default 10."
          }
        },
        "required": [
          "planId",
          "mode"
        ],
        "additionalProperties": false
      },
      "page": "/en"
    }
    read_current_viewAnswer

    Call this when a tool returned stalePlan, or to learn which screen the app is on (home, directions, place, nearby) and what it shows: the search query and counts, the directions fields and plan summary, or the place and its info axes.

    View tool JSON
    {
      "name": "read_current_view",
      "kind": "answer",
      "impl": "imperative",
      "description": "Call this when a tool returned stalePlan, or to learn which screen the app is on (home, directions, place, nearby) and what it shows: the search query and counts, the directions fields and plan summary, or the place and its info axes.",
      "inputSchema": {
        "type": "object",
        "properties": {},
        "additionalProperties": false
      },
      "page": "/en"
    }