Skip to main content
Glama

drop_item

Destructive

Unload the carried item at the station or shelf where the specified robot is standing.

Instructions

Unload the carried item at the station or shelf the robot is standing at.

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>"
    },
    "name": "drop_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
robot_idYesRobot id, e.g. amr_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already flag this as destructive, non-idempotent, and not read-only, so the safety profile is known. The description adds the useful precondition that the robot must be at a station/shelf, but says nothing about what happens on failure, whether a held item is lost, or whether the release point is precise.

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 sentence with no filler, front-loading the action and folding the location constraint into the same clause.

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?

For a one-parameter, no-output-schema tool whose annotations cover the safety profile, this is close to adequate. However, for a destructive operation it omits error/failure behavior and whether the item is released at the robot's exact pose, leaving the agent to guess edge cases.

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?

Only one parameter, robot_id, and schema description coverage is 100% with an example value ('amr_1'). The description adds no meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Unload') and object ('the carried item') plus the spatial precondition ('at the station or shelf the robot is standing at'). This makes it clearly the inverse of pick_item, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied: the robot must be carrying an item and standing at a station or shelf. There is no explicit when-to-use/when-not guidance, no failure conditions (e.g., nothing held, wrong location), and no named alternative.

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