Skip to main content
Glama

Tip the driver

tip_driver
Destructive

Cents, from your wallet. Reuse idempotency_key when retrying the same tip.

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>",
      "idempotency_key": "<idempotency_key>",
      "amount_cents": "<amount_cents>"
    },
    "name": "tip_driver"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYes
amount_centsYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is partly covered. The description adds genuine context beyond that: funds come 'from your wallet' (a balance dependency) and retries with a reused idempotency_key are deduplicated. It omits whether the tip is reversible, what happens on insufficient balance, and any rate limit.

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

Conciseness3/5

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

Very short with no padding, but the first sentence is a noun-phrase fragment rather than a statement, and the wallet/idempotency facts are compressed into two telegraphic clauses. It is terse without being well-structured for an agent reading it cold.

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 three-required-parameter money-moving tool with no output schema, the definition is thin: it never explains delivery_id's role, doesn't say what is returned (tip confirmation, new balance), and doesn't note the amount ceiling. Annotations carry the destructive/openWorld signal, but the description leaves meaningful gaps.

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 description coverage is 0%, so the description has to compensate. It explains two of three parameters well: amount_cents is denominated in cents and idempotency_key is for retrying the same tip. delivery_id is never mentioned, and the 50–50000 cent bounds exist only in the schema.

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

Purpose3/5

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

The description opens with the fragment 'Cents, from your wallet,' which supplies the unit and funding source but never states the verb or resource itself. The purpose ('tip the driver') only becomes clear by reading the title, and nothing in the text separates this from siblings like rate_driver or send_message_to_driver.

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?

The only usage guidance is the retry instruction 'Reuse idempotency_key when retrying the same tip.' There is no statement of when to tip versus use rate_driver, no prerequisite checks (delivery completed? wallet funded?), and no indication of when not to call it.

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.