Skip to main content
Glama

Get delivery estimate

wise_get_delivery_estimate
Read-only

Get the expected arrival date for a Wise transfer using its transfer ID, with an optional timezone to show local delivery timing.

Instructions

Get when a transfer is expected to arrive.

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": {
      "transferId": "<transferId>"
    },
    "name": "wise_get_delivery_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNoe.g. Europe/London
transferIdYesTransfer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond them: it does not say what happens for cancelled, pending, or already-delivered transfers, nor whether the estimate can be absent or null. Given a read-only network call with no output schema, that is a meaningful gap.

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 short sentence with no filler, and the verb-resource pairing is front-loaded. It is efficient, though its brevity borders on under-specification for a tool whose behavior across transfer states is non-obvious.

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 two-parameter read-only tool with no output schema, the description covers what is returned at a high level. However, it omits the shape of the result (a date/time vs. a range) and any caveats about when an estimate is unavailable, leaving the agent to discover failure modes 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?

Schema description coverage is 100%, so both transferId and timezone are already documented in the schema, including an example format for timezone. The description contributes no additional meaning about which transfer ID to supply or how timezone affects the returned estimate. Baseline 3 applies.

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?

States a specific verb and resource: retrieving the expected arrival timing for a transfer. It is distinguishable from wise_get_transfer, which returns transfer details rather than timing, but the description does not name or contrast any sibling explicitly.

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?

No guidance on when to call this versus wise_get_transfer or wise_get_quote, and no prerequisites stated (e.g. whether the transfer must be funded or in a specific state). The agent must infer usage entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.