Skip to main content
Glama
harshil1712

Berlin Transport MCP Server

by harshil1712

get_journeys

Plan public transport routes in Berlin by entering origin and destination stop IDs to receive journey options with departure times.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesOrigin stop ID
toYesDestination stop ID
departureNoDeparture time (e.g. tomorrow 2pm)
resultsNoNumber of results to return

Implementation Reference

  • Handler function that fetches journeys from origin to destination using the VBB Transport API by constructing the appropriate URL and returning JSON data as text.
    async ({ from, to, departure, results }) => {
      const url = new URL("/journeys", VBB_API_BASE);
      url.searchParams.set("from", from);
      url.searchParams.set("to", to);
      if (departure) {
        url.searchParams.set("departure", departure);
      }
      if (results) {
        url.searchParams.set("results", String(results));
      }
    
      const response = await fetch(url);
      const data = await response.json();
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Zod input schema defining parameters for the get_journeys tool: from (origin), to (destination), optional departure time, and optional number of results.
    {
      from: z.string().describe("Origin stop ID"),
      to: z.string().describe("Destination stop ID"),
      departure: z
        .string()
        .optional()
        .describe("Departure time (e.g. tomorrow 2pm)"),
      results: z.number().optional().describe("Number of results to return"),
    },
  • src/index.ts:57-85 (registration)
    Registration of the get_journeys tool on the MCP server, including name, input schema, and handler function.
    this.server.tool(
      "get_journeys",
      {
        from: z.string().describe("Origin stop ID"),
        to: z.string().describe("Destination stop ID"),
        departure: z
          .string()
          .optional()
          .describe("Departure time (e.g. tomorrow 2pm)"),
        results: z.number().optional().describe("Number of results to return"),
      },
      async ({ from, to, departure, results }) => {
        const url = new URL("/journeys", VBB_API_BASE);
        url.searchParams.set("from", from);
        url.searchParams.set("to", to);
        if (departure) {
          url.searchParams.set("departure", departure);
        }
        if (results) {
          url.searchParams.set("results", String(results));
        }
    
        const response = await fetch(url);
        const data = await response.json();
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/harshil1712/berlin-transport-mcp'

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