Skip to main content
Glama

pick_item

Destructive

Load a specified item from the shelf where a given warehouse robot is standing by providing the robot ID and item name.

Instructions

Load an item from the 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>",
      "item": "<item>"
    },
    "name": "pick_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
robot_idYesRobot id, e.g. amr_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, destructive, non-idempotent, non-open-world action, so the safety profile is covered. The description adds a useful physical precondition (the robot must be standing at the target shelf), but says nothing about failure behavior, whether the shelf inventory is decremented, or what happens if the gripper is occupied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words; the spatial constraint is placed immediately after the action. It is arguably too terse for a destructive physical operation, but nothing in it is redundant.

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

Completeness2/5

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

For a destructive physical manipulation tool with no output schema and an undocumented required parameter, the description is thin. It omits whether the item is removed from shelf state, what constitutes success or failure, and how the item argument should be formatted.

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?

Schema description coverage is only 50%: robot_id is documented in the schema while item is a bare string. The description could compensate by explaining the item identifier format (SKU, name, or listed location) but adds no meaning beyond 'an item', leaving the more ambiguous parameter undocumented.

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 concrete physical action (load an item) plus the spatial constraint that identifies which shelf is used ('the shelf the robot is standing at'). This clearly separates it from the inverse sibling drop_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 rather than stated: the agent can infer this is the pick half of a pick-and-place flow before drop_item. It never states prerequisites such as the robot already being navigated to the shelf location or having an empty gripper, and no explicit when-not-to-use is given.

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