How do I get the EVA station number for a station?

Use the station search endpoint with a name pattern: it returns the matching stations and their EVA station numbers. You then pass that EVA number to the planned-timetable and change endpoints, which identify a station by its EVA number rather than its name.

What are the rate limits for the Deutsche Bahn Timetables API?

The OpenAPI spec does not state rate limits, and quotas are managed through the DB API Marketplace. Check the official documentation at https://developers.deutschebahn.com/ for current limits before heavy polling.

How do I read German train timetables through Jentic?

Add the Deutsche Bahn Timetables API from the Jentic API Directory and connect your DB-Api-Key and DB-Client-Id once. Your agent then searches by intent such as 'planned timetable for a station' and calls the matching operation. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Deutsche Bahn API?

Yes. All four operations are read-only GETs, so you grant your agent only the ones it needs, such as station search and the timetable lookup while leaving out the change feeds. The EVA number sits in the URL path, so a rule can also pin the agent to specific path operations, and every call is logged.

Is there a Deutsche Bahn timetable MCP server?

You don't need an MCP server to give your agent Deutsche Bahn timetables. Jentic connects it directly from the API Directory: import it, connect your keys once, and your agent can search stations and read timetables without another server loading tool definitions into its context.