Skip to main content
Glama

Tankful: Irish heating oil prices

Review delivery options

tankful_delivery_request_draft
Read-onlyIdempotent

Use this when someone wants to go ahead and arrange a delivery in the Republic of Ireland. Prepares county, fuel, 300 to 5000 whole litres and timing, and returns a link to finish on Tankful. Agents can't place the order. Does not send to anyone, create a persisted request, reserve, take payment or collect personal details.

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": {
      "county": "<county>",
      "litres": "<litres>"
    },
    "name": "tankful_delivery_request_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelNoKEROSENE
countyYesRepublic of Ireland county; do not provide an address or Eircode.
litresYes
urgencyNoTHIS_WEEK

Output Schema

NameRequiredDescriptionDefault
fuelNo
kindYes
guideNo
titleYes
countyNoRepublic of Ireland county; do not provide an address or Eircode.
litresNo
messageYes
urgencyNo
checkedAtYes
suppliersNo
continuationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description goes further by enumerating what does NOT happen: no sending, no persisted request, no reservation, no payment, no personal-detail collection. That negative-space disclosure is exactly the context an agent needs before promising a user anything, and it is consistent with the read-only, non-destructive annotations.

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 sentences, zero filler: the trigger comes first, the inputs and return value second, the negative boundaries last. Every sentence carries load and nothing is repeated from the schema or annotations verbatim beyond the useful litre range.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and rich annotations, the description need only cover trigger, scope and side effects, and it does all three, including the Ireland-only limit and the hand-off link. Nothing an agent needs in order to call this correctly or describe the result to a user is missing.

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?

Schema description coverage is only 25% (only county is documented), so the description must compensate, and it does: it names all four inputs and restates the 300–5000 whole-litre constraint, reinforcing the schema minimum/maximum. It does not explain the fuel enum values or what the urgency options mean, leaving some semantic gap.

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 action (prepares county, fuel, litres and timing, then returns a link to finish on Tankful) rather than a vague verb, and scopes it geographically to the Republic of Ireland. It is clearly distinguishable from the sibling price/supplier/orders tools because it says the output is a completion link, not pricing data or an order.

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

Usage Guidelines4/5

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

The trigger is explicit: 'Use this when someone wants to go ahead and arrange a delivery,' and 'Agents can't place the order' tells the agent where its role stops. It never names a sibling tool as the alternative for price research or order status, so the routing guidance is clear but not exhaustive.

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