Skip to main content
Glama

autonomy_stop

Stops autonomous driving and applies full braking to safely halt the vehicle in simulation.

Instructions

Stop autonomous driving and apply full braking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNooperator_stop

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
backendNo
runningYes
confidenceNo
started_atNo
target_fpsNo
vehicle_idNo
frame_age_msNo
hazard_scoreNo
inference_msNo
last_controlNo
measured_fpsNo
watchdog_armedNo
watchdog_tripsNo
watchdog_reasonNo
emergency_reasonNo
watchdog_latchedNo
emergency_stoppedNo
perception_deviceNo
engine_deadman_armedNo
perception_providersNo
engine_deadman_last_errorNo
engine_deadman_expires_in_msNo
engine_deadman_lease_secondsNo
engine_deadman_control_authorizedNo
engine_deadman_last_renewal_age_msNo
Behavior4/5

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

The description adds the behavioral detail of applying full braking, which goes beyond the annotations. Annotations are consistent with a state-changing action.

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 a single, focused sentence that front-loads the action. No unnecessary words.

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?

While the core action is clear, the lack of parameter explanation and usage guidance makes it only minimally adequate for a tool with a single optional parameter and an output schema.

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

Parameters2/5

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

The description does not mention the 'reason' parameter, and schema description coverage is 0%. The agent must infer the parameter's purpose from its name and default value.

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 clearly states the verb 'Stop' and the resource 'autonomous driving', with the additional action 'apply full braking'. This distinguishes it from siblings like 'autonomy_start' and 'emergency_stop'.

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?

No guidance is provided on when to use this tool versus alternatives like 'emergency_stop'. There is no mention of prerequisites or context.

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/eric-rolph/beamng-mcp'

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