Skip to main content
Glama

Message the driver

send_message_to_driver

Delivered as a push + in-app message once a driver is assigned.

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

Input Schema

NameRequiredDescriptionDefault
bodyYes
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already establish write, non-idempotent, open-world, non-destructive semantics, so the bar is lower. The description adds two real behavioral facts not in the annotations: the message is delivered via push plus in-app, and a driver must already be assigned. It does not disclose whether messages are persisted/logged, what happens on retry given non-idempotency, or any rate limits.

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?

A single short sentence with no filler, but it is a passive fragment that front-loads the delivery mechanism instead of the action. Brevity here comes at the cost of substance rather than from efficiency.

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?

This is a real-world side-effecting send (openWorldHint true, non-idempotent) with no output schema and no schema descriptions, so the description is the only place behavioral detail can live. One fragment cannot cover error behavior when no driver is assigned, the effect of duplicate sends, or what body will look like to the driver.

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 0% for both parameters, so the description must carry the load, and it effectively does not: neither 'delivery_id' nor 'body' is explained, and the 2000-character body limit appears only in the schema. The clause 'once a driver is assigned' weakly implies delivery_id must reference a delivery with an assigned driver, which is the only parameter-relevant inference offered.

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 is a sentence fragment with no active verb for the tool's action; it describes the delivery channel ('push + in-app message') rather than stating 'sends a message to the driver assigned to a delivery'. Combined with the tool name the purpose is inferable, but the description itself never commits to what the tool does or which resource the message targets.

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-relevant content is the precondition 'once a driver is assigned', which usefully implies the tool fails or is inapplicable before assignment. There is no guidance on when to choose this over siblings like get_delivery_messages, rate_driver, or tip_driver, and no exclusions or state requirements.

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.