Skip to main content
Glama

route_generate

Assigns shortest-path routes to trips using the road network, converting trip files into route files required for SUMO simulation.

Instructions

[Step 4/5] Generate routes from trips using SUMO's duarouter.

Assigns shortest-path routes to each trip based on the road network.
Converts trips.xml → routes.rou.xml which is required for simulation.

Previous step: trip_generate() to get .trips.xml file.
Next step: sumo_runner() to run the simulation with net_file and route_file.

=== PARAMETERS ===
- net_file (REQUIRED): Path to SUMO network file (.net.xml, from net_convert)
- trip_file (REQUIRED): Path to trip file (.trips.xml, from trip_generate)

=== RETURNS ===
- route_file: Path to generated .rou.xml file (pass to sumo_runner)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
net_fileYes
trip_fileYes
output_dirNooutput/trips

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries full burden. It states that routes are assigned using shortest-path and that the output is a .rou.xml file. It does not disclose potential side effects, resource usage, or error conditions. Basic behavioral traits are implied but insufficient.

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 concise, well-structured with sections for step context, parameters, and returns. Every sentence adds value without redundancy. The workflow markers are efficient.

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

Completeness4/5

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

Given the tool's role in a pipeline, the description adequately covers purpose, parameters, and return value. It connects to sibling tools. The only gap is the undocumented output_dir parameter. The presence of an output schema (context signal) does not affect the score as it is not shown.

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?

Schema coverage is 0%, so description must compensate. It explains net_file and trip_file with provenance (from net_convert and trip_generate). The third parameter output_dir is not mentioned, though it has a default. The description adds meaningful context beyond the schema, but missing one parameter prevents a higher score.

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

Purpose5/5

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

The description explicitly states 'Generate routes from trips using SUMO's duarouter' and explains the conversion from trips.xml to routes.rou.xml. It distinguishes the tool from siblings by referencing the workflow steps (trip_generate and sumo_runner).

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

Usage Guidelines4/5

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

The description provides clear workflow context: 'Previous step: trip_generate()' and 'Next step: sumo_runner()'. This tells the agent when to use the tool. However, it does not explicitly mention alternatives or scenarios where the tool should not be used.

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/urban-ai-institute/kra35-prismx-agentsumo'

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