Skip to main content
Glama

speed_limit_edit_tool

Modify speed limits on specific road segments using a target road name or location with a radius, enabling localized speed changes for SUMO traffic simulations.

Instructions

Modify speed limits on specific road segments (supports partial application).

✅ Trip file can be reused - edges still exist, only speed limit changed.
Workflow: speed_limit_edit → sumo_runner (reuse existing trip file)

REALISTIC USAGE: Use reference_location + radius_km for localized speed limit changes!

Examples:
    # REALISTIC: Reduce speed to 40km/h on 500m of Teheran-ro near Gangnam Station
    speed_limit_edit_tool(
        net_file="gangnam_station.net.xml",
        target_road_name="테헤란로",
        reference_location="강남역",
        radius_km=0.5,
        new_speed_kmph=40.0
    )
    # Then: sumo_runner (reuse trip file - no trip_generate needed!)

Args:
    net_file: Network file path
    route_file: Route file path (optional, can be reused after this tool)
    output_dir: Output directory for results
    target_road_name: Road name (e.g., '테헤란로')
    edge_ids: Specific edge IDs (optional)
    reference_location: Reference point (optional, e.g., "강남역")
    radius_km: Radius in km (optional, e.g., 0.5)
    new_speed_kmph: New speed limit in km/h (e.g., 40.0)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
edge_idsNo
net_fileYes
radius_kmNo
output_dirNooutput/networks
route_fileNo
new_speed_kmphNo
target_road_nameNo
reference_locationNo
Behavior4/5

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

Discloses non-destructive behavior: 'Trip file can be reused - edges still exist, only speed limit changed.' No annotations provided, so description carries burden. Could mention if modifications are reversible or output file location, but overall transparency is good.

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?

Well-structured with sections: workflow, realistic usage, examples, and Args list. Front-loaded with purpose. Every sentence adds value, no fluff. Appropriate length for a complex tool.

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?

Covers main use cases, workflow, and parameter details. With 8 parameters and no output schema, description provides enough context for typical usage. However, it could explicitly mention what the tool outputs (e.g., modified net file) to be fully complete.

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 has 0% description coverage, but description adds brief yet useful parameter explanations with example values (e.g., reference_location='강남역'). Clarifies optionality and usage for all parameters, compensating for schema gaps.

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?

Explicitly states 'Modify speed limits on specific road segments' with a specific verb and resource. Distinguishes from siblings like edge_edit_tool by focusing on speed limits and mentioning partial application and reuse of trip files.

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

Usage Guidelines5/5

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

Provides a clear workflow (speed_limit_edit → sumo_runner) and realistic usage advice (use reference_location and radius_km). Examples show how to call the tool and interpret parameters. Explicitly states when to reuse trip file, guiding against unnecessary regeneration.

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