Skip to main content
Glama

Agua e Vida — On-Demand Purified Water Delivery & Refills

check_delivery_coverage

Check if a delivery address or suburb in Pretoria/Gauteng is eligible for doorstep purified water delivery, and calculate estimated delivery fees.

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": {
      "address_or_suburb": "<address_or_suburb>"
    },
    "name": "check_delivery_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
address_or_suburbYesThe delivery street address or suburb name (e.g. "Faerie Glen, Pretoria", "Moreleta Park", "Silver Lakes")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address_or_suburb / description
      Previous value: -"The delivery street address or suburb name (e.g. \"Faerie Glen, Pretoria\", \"Moreleta Park\", \"Silver Lakes\") [Required: non-empty valid value must be supplied]."New value: +"The delivery street address or suburb name (e.g. \"Faerie Glen, Pretoria\", \"Moreleta Park\", \"Silver Lakes\")"
  2. Changed1 schema field changed
    • changedInput schema / properties / address_or_suburb / description
      Previous value: -"The delivery street address or suburb name (e.g. \"Faerie Glen, Pretoria\", \"Moreleta Park\", \"Silver Lakes\")"New value: +"The delivery street address or suburb name (e.g. \"Faerie Glen, Pretoria\", \"Moreleta Park\", \"Silver Lakes\") [Required: non-empty valid value must be supplied]."
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. The verbs 'check' and 'calculate' imply a non-destructive, read-only lookup and disclose that fees are estimated, but nothing is said about what the response contains (eligibility flag, fee breakdown), whether results are cached, or any auth/rate-limit constraints.

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?

One tightly written sentence with the action and scope front-loaded and zero filler. Nothing needs trimming or reordering.

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 one-parameter tool with no output schema and no annotations, the definition should describe the shape of the answer (eligible/ineligible plus estimated fee). It omits return-value expectations entirely, leaving the agent to discover the result format at call time.

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?

With a single parameter and 100% schema description coverage including concrete examples, the schema already does the documentation work. The description adds a geographic scope constraint (Pretoria/Gauteng) not present in the schema, but offers no format guidance beyond what the schema provides.

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

Purpose5/5

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

States a specific verb+resource pair (check delivery coverage / calculate delivery fees) with a clear domain: doorstep purified water delivery in Pretoria/Gauteng. An agent can instantly distinguish this from siblings like create_checkout_cart, list_products, or track_order_status.

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?

The description implies the usage context (verifying serviceability before ordering) and bounds the geography to Pretoria/Gauteng, but never states explicitly when to call it versus alternatives such as create_checkout_cart, nor any prerequisites or exclusions.

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