Skip to main content
Glama
serve-delivery-mcp

serve-delivery-mcp

by edtechniti

Unlock robot bin

unlock_robot_bin

Opens a delivery robot's cargo bin so the recipient can collect items after the robot arrives at the dropoff. Use it to complete handoff only when the robot has reached the destination.

Instructions

Open the robot's cargo bin so the recipient can collect the items. Only works once the robot has arrived at the dropoff.

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": {
      "delivery_id": "<delivery_id>"
    },
    "name": "unlock_robot_bin"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYesDelivery id returned by dispatch_robot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is not read-only and not destructive, and the description adds a real behavioral constraint (arrival prerequisite) beyond that. It does not disclose what happens on a premature call (error vs. no-op), whether the call is idempotent, or whether the bin can be re-locked, which are meaningful gaps for a physical-world 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?

Two sentences, zero filler, with the action stated first and the precondition second. Nothing could be removed without losing information.

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?

For a one-parameter action with no output schema and annotations covering the safety profile, the definition supplies what an agent needs to attempt the call correctly. The remaining gap is failure behavior when the arrival condition is unmet.

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?

The single parameter is fully documented in the schema, including the key hint that the id comes from dispatch_robot. The description adds nothing about delivery_id, so the baseline 3 for high schema coverage 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 and resource — "Open the robot's cargo bin" — plus the intent (recipient collects items), which is unambiguous against siblings like dispatch_robot or cancel_delivery. It stops short of explicitly contrasting with any sibling, but the action is distinct enough that no confusion arises.

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

Usage Guidelines4/5

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

"Only works once the robot has arrived at the dropoff" is a concrete precondition that tells the agent when the call is valid, including the likely failure mode of calling too early. It does not name alternatives or say what to do instead if the robot has not arrived, which keeps it out of the top band.

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