Skip to main content
Glama

dock

Destructive

Send a specified robot to an available charging station and charge it to 100%.

Instructions

Drive a robot to a free charging dock and charge it to 100 %.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "robot_id": "<robot_id>",
      "dock": "<dock>"
    },
    "name": "dock"
  }
}

Input Schema

NameRequiredDescriptionDefault
dockYesLocation name from list_locations
robot_idYesRobot id, e.g. amr_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the risk profile is covered structurally. The description adds that the dock must be 'free' (implying the tool occupies/reserves it) and that charging runs to 100 %, but it never says whether the call blocks until charging finishes, whether an in-progress task is aborted, or what happens if no free dock exists. Given the annotations, a 3 is appropriate but the mutation semantics remain thin.

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?

A single, front-loaded sentence with no filler; every clause (drive, free dock, charge to 100 %) carries information.

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?

With no output schema the description must stand in for return behavior, and for a destructive, non-idempotent operation it omits whether the call is blocking, how failures are surfaced, and whether the robot's current task is preempted. It is adequate for a simple two-parameter tool but not complete for a state-changing one.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are fully documented in the schema, so the baseline is 3. The description's word 'free' adds only marginal meaning by hinting the dock argument should reference an available location from list_locations, but it does not elaborate on the robot_id format beyond the schema example.

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

Purpose4/5

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

The description names a specific verb ('Drive...and charge') and resource ('a free charging dock'), and the 'charge it to 100 %' clause makes the goal distinct from a plain navigation call such as navigate_to. It is clear what the tool accomplishes without opening the schema, though it never explicitly contrasts itself with siblings.

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?

There is no explicit when-to-use or when-not-to-use guidance; the reader must infer that this is for recharging a robot. Nothing tells the agent how this differs from navigate_to plus a separate charging step, nor whether it should be preferred when the robot is mid-task.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.