Skip to main content
Glama

GELATO.cz

Delivery addresses

list_delivery_addresses
Read-only

Delivery addresses registered for this customer. Use the returned id as delivery_address_id in place_order when the customer has more than one. A brand-new customer has none yet — call create_delivery_address first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_delivery_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds non-obvious behavioral context: the result is empty for new customers, and the id field is the intended hand-off value to place_order. It does not mention ordering, pagination, or fields returned, but for a zero-param list that is a minor gap.

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: what it is, how to use the result, and the empty-state remedy. Front-loaded and every sentence carries information an agent needs.

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?

With no output schema, the description carries the burden of explaining returns, and it identifies the key field (id) plus the empty-result case. It stops short of describing the other address fields returned (street, city, default flag, etc.), which would fully close the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no input parameters, so the baseline is 4. The description does clarify the semantics of the returned id and its role as delivery_address_id, which is useful even though nothing is passed in.

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 the resource ('delivery addresses') and its scope ('registered for this customer'), which is enough to distinguish it from create_delivery_address and the order/cart siblings. It reads as a noun phrase rather than an explicit verb, but the listing intent is unambiguous.

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

Usage Guidelines5/5

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

It gives explicit downstream usage ('use the returned id as delivery_address_id in place_order when the customer has more than one') and a clear prerequisite path ('A brand-new customer has none yet — call create_delivery_address first'). An agent knows both when to call it and what to do with the result.

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.

Resources