Skip to main content
Glama

Create a private handover code

create_recipient_code
Destructive

Generate or replace a six-digit code for a delivery stop requiring OTP proof. Share it privately with the intended recipient, never the driver. Replacing invalidates the old code. Expires in seven days; five failed attempts lock it.

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

Input Schema

NameRequiredDescriptionDefault
stop_idYes
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

The annotations only hint that this is a non-idempotent, destructive write, but the description explains exactly what is destroyed ('replacing invalidates the old code') and adds two operational limits not present anywhere in structured fields: a seven-day expiry and a five-failed-attempt lockout. That is precisely the extra context a caller needs before invoking a destructive mutation.

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?

Three short sentences, front-loaded with the action, then handling guidance, then lifecycle constraints. No sentence is redundant and every clause carries information a caller would otherwise lack.

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 two-parameter mutation with no output schema, the description covers the lifecycle (generation, replacement, expiry, lockout) and safe handling of the secret. It stops short of a few things, such as what is returned or what happens when a stop does not actually require OTP, but nothing essential to calling it correctly is missing.

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?

Both required parameters (delivery_id, stop_id) have 0% schema description coverage, and the description never mentions them individually — 'for a delivery stop' only weakly implies that the pair identifies the stop. With low coverage the description is expected to compensate, and it does not, leaving the caller to infer the id semantics from parameter names alone.

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 ('Generate or replace') and resource ('six-digit code for a delivery stop requiring OTP proof'), plus the title reinforces that it is a private handover code. It is unambiguous what the tool does, though it does not explicitly contrast with any sibling, and the sibling list contains no tool that could be confused with it.

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?

It carves out a clear usage condition (delivery stops requiring OTP proof) and gives a handling rule for the output ('share it privately with the intended recipient, never the driver'). What is missing is guidance on when to prefer generating a fresh code versus replacing an existing one, or what to do when a stop does not require OTP.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.