Skip to main content
Glama
yunkee-lee

MCP TMAP Server

by yunkee-lee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SK_OPEN_API_APP_KEYYesYour SK open API app key credentials

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
publicTransitRoutesB

Retrieves public transportation routes from start to destination.

Args: startLon (str): longitude of the starting point (WSG84). startLat (str): latitude of the starting point (WSG84). destLon (str): longitude of the destination (WSG84). destLat (str): latitude of the destination (WSG84). language (int): language of the route; 0 for Korean and 1 for English. searchTime (str, optional): Sets the time for the route to be searched. Used as information to indicate whether transportation is in operation. See [service] in the response for the operation status.

Returns: route information

  • itineraries: route details

    • fare: total fare

    • totalTime: in seconds

    • transferCount:

    • totalWalkDistance: in meters

    • totalDistance: in meters

    • totalWalkTime: in seconds

    • legs: legs in the route

      • distance: in meters

      • sectionTime: in seconds

      • mode: transportation mode

      • route: transportation route

      • start: starting point of the leg

      • end: destination of the leg

fullTextAddressGeocodingC

Converts the given address to coordinates (geocoding).

Args address (str): address to convert.

Returns: a list of coordinates

  • newLat: latitude

  • newLon: longitude

  • newLatEntr: latitude of the entrance

  • newLonEntr: longitude of the entrance

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: one is for geocoding addresses to coordinates, and the other is for retrieving public transit routes between coordinates. There is no overlap in functionality, making it impossible to confuse them.

Naming Consistency2/5

The naming is inconsistent: 'fullTextAddressGeocoding' uses camelCase, while 'publicTransitRoutes' uses a different style with mixed lower and upper case. There is no clear pattern, and the verb usage differs ('fullTextAddress' vs. 'publicTransit'), making it chaotic.

Tool Count2/5

With only 2 tools, the server feels thin for a mapping/transit domain. It lacks basic operations like reverse geocoding, route alternatives, or transit schedule details, making it under-scoped for typical navigation or location-based tasks.

Completeness2/5

The server is severely incomplete for a mapping/transit service. It misses essential operations such as reverse geocoding, route optimization, transit stop information, or map data retrieval. The two tools provide only a narrow slice of functionality, leading to significant gaps in agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources