Skip to main content
Glama

travel_times

Get real-time estimated travel times for Singapore expressway segments. This tool provides updated traffic data every 5 minutes to help plan routes and avoid congestion.

Instructions

Get estimated travel times on expressway segments. Updates every 5 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the travel_times tool by making an API request to LTA's estimated travel times endpoint and returning the response data or handling errors.
    case "travel_times": {
      try {
        const response = await axios.get('https://datamall2.mytransport.sg/ltaodataservice/EstTravelTimes', {
          headers: {
            'AccountKey': process.env.LTA_API_KEY!,
            'accept': 'application/json'
          }
        });
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }]
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          return {
            content: [{
              type: "text",
              text: `LTA API error: ${error.response?.data?.Message ?? error.message}`
            }],
            isError: true
          };
        }
        throw error;
      }
    }
  • Tool schema definition including name, description, and input schema (no required parameters) returned by the ListTools handler.
    {
      name: "travel_times",
      description: "Get estimated travel times on expressway segments. Updates every 5 minutes.",
      inputSchema: {
        type: "object",
        properties: {} // No parameters needed
      }
    },
  • src/index.ts:47-130 (registration)
    The tool is registered by being included in the tools list returned by the ListToolsRequestSchema handler.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [{
          name: "bus_arrival",
          description: "Get real-time bus arrival information for a specific bus stop and optionally a specific service number. Returns estimated arrival times, bus locations, and crowding levels.",
          inputSchema: {
            type: "object",
            properties: {
              busStopCode: {
                type: "string",
                description: "The unique 5-digit bus stop code"
              },
              serviceNo: {
                type: "string",
                description: "Optional bus service number to filter results"
              }
            },
            required: ["busStopCode"]
          }
        },
        {
          name: "station_crowding",
          description: "Get real-time MRT/LRT station crowdedness level for a particular train network line. Updates every 10 minutes.",
          inputSchema: {
            type: "object",
            properties: {
              trainLine: {
                type: "string",
                description: "Code of train network line (CCL, CEL, CGL, DTL, EWL, NEL, NSL, BPL, SLRT, PLRT, TEL)",
                enum: ["CCL", "CEL", "CGL", "DTL", "EWL", "NEL", "NSL", "BPL", "SLRT", "PLRT", "TEL"]
              }
            },
            required: ["trainLine"]
          }
        },
        {
          name: "train_alerts",
          description: "Get real-time train service alerts including service disruptions and shuttle services. Updates when there are changes.",
          inputSchema: {
            type: "object",
            properties: {} // No parameters needed
          }
        },
        {
          name: "carpark_availability",
          description: "Get real-time availability of parking lots for HDB, LTA, and URA carparks. Updates every minute.",
          inputSchema: {
            type: "object",
            properties: {} // No parameters needed
          }
        },
        {
          name: "travel_times",
          description: "Get estimated travel times on expressway segments. Updates every 5 minutes.",
          inputSchema: {
            type: "object",
            properties: {} // No parameters needed
          }
        },
        {
          name: "traffic_incidents",
          description: "Get current road incidents including accidents, roadworks, and heavy traffic. Updates every 2 minutes.",
          inputSchema: {
            type: "object",
            properties: {} // No parameters needed
          }
        },
        {
          name: "station_crowd_forecast",
          description: "Get forecasted MRT/LRT station crowdedness levels in 30-minute intervals.",
          inputSchema: {
            type: "object",
            properties: {
              trainLine: {
                type: "string",
                description: "Code of train network line (CCL, CEL, CGL, DTL, EWL, NEL, NSL, BPL, SLRT, PLRT, TEL)",
                enum: ["CCL", "CEL", "CGL", "DTL", "EWL", "NEL", "NSL", "BPL", "SLRT", "PLRT", "TEL"]
              }
            },
            required: ["trainLine"]
          }
        }]
      };
    });
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about the update frequency ('Updates every 5 minutes'), which helps set expectations for data freshness. However, it lacks other important behavioral details such as whether this is a read-only operation, potential rate limits, error conditions, or what the output format looks like (especially critical since there's no output schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly concise and well-structured with just two sentences. The first sentence clearly states the core purpose, and the second adds important behavioral context about update frequency. Every word earns its place with zero waste or redundancy, making it easy for an agent to parse quickly.

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

Completeness3/5

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

Given the tool's moderate complexity (travel time estimation with dynamic updates) and the absence of both annotations and an output schema, the description is incomplete. While it covers the purpose and update frequency adequately, it lacks crucial information about what the tool returns (format, structure, units) and any operational constraints. For a tool with no output schema, the description should ideally explain the return values, which it doesn't do.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters. The baseline for 0 parameters with high schema coverage is 4, as the description correctly focuses on other aspects without unnecessary parameter discussion.

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?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('estimated travel times on expressway segments'), making it immediately understandable. It distinguishes itself from siblings like traffic_incidents or train_alerts by focusing on travel time estimates rather than incidents or alerts. However, it doesn't explicitly differentiate from all siblings (e.g., bus_arrival might also involve travel estimates).

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when this tool is appropriate compared to siblings like traffic_incidents (for disruptions) or station_crowding (for congestion at stations), nor does it specify any prerequisites or exclusions. The only contextual hint is the update frequency, which doesn't help with tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arjunkmrm/mcp-sg-lta'

If you have feedback or need assistance with the MCP directory API, please join our Discord server