Skip to main content
Glama

Rate the driver

rate_driver
Idempotent

Rate the driver of a completed delivery from 1 to 5 stars, with an optional comment.

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>",
      "stars": "<stars>"
    },
    "name": "rate_driver"
  }
}

Input Schema

NameRequiredDescriptionDefault
starsYes
commentNo
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the agent knows this is a non-destructive, repeatable write. The description adds the useful 'completed delivery' precondition, but omits what happens if the delivery is not completed, whether the rating is final/visible to the driver, and any permission requirements.

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 zero filler and the key constraint (value range, optionality) placed inline. Minor waste comes from restating the title verbatim at the start.

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 mutation tool with 0% schema description coverage and no output schema, the definition is thin: it never explains delivery_id semantics, error cases (unknown or incomplete delivery), or whether repeated calls overwrite the prior rating despite idempotentHint=true. The annotations soften the safety gap but not the input-documentation gap.

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 must carry parameter meaning. It clarifies that 'stars' is a 1-5 scale and that 'comment' is optional, but the range merely repeats the schema's minimum/maximum, and 'delivery_id' is left completely unexplained beyond the generic 'completed delivery' phrase.

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 gives a specific verb+resource ('Rate the driver') plus the value domain ('1 to 5 stars') and the optional comment, which is clearly distinct from retrieval or messaging tools. It does not, however, explicitly contrast itself with adjacent tools like tip_driver or send_message_to_driver, so an agent must infer the boundary.

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?

'of a completed delivery' implies a precondition (the delivery must be finished) and thus an implied when-to-use. There is no explicit when-not guidance, no statement of whether a rating can be changed after submission, and no mention of alternatives such as tipping the same driver.

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.