Skip to main content
Glama

Quote withdrawal

jami_quote_withdrawal
Read-onlyIdempotent

Preview an Ethiopian birr withdrawal offline without API calls or a token: see fees, tax, net amount, auto-pay or manual review, and the rolling 24h cap.

Instructions

Preview what reaches the destination for a withdrawal — offline, no API call, works without a token.

The JamiDev usage fee (7% unless Jami set a custom rate on the account) and any government tax are cut FROM the amount: you withdraw amount, the account receives net. Rounding is round-half-up per component. The server is authoritative; the real breakdown comes back on the withdrawal.

Args:

  • amount_minor: gross santim (min 10000 = 100.00 ETB).

  • fee_rate / tax_rate: optional overrides (0–1) if you know the account's real rates.

Returns the breakdown plus whether the amount auto-pays (≤ 10,000 ETB) or goes to manual review, and the per-org 100,000 ETB rolling-24h cap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fee_rateNo
tax_rateNo
amount_minorYesGross amount in integer santim — the fee is cut from this. 10000 = 100.00 ETB (the minimum).
response_formatNo'markdown' (default) for a readable summary, 'json' for the full structured payloadmarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fee_rateYes
tax_rateYes
fee_minorYes
net_minorYes
tax_minorYes
auto_payoutYestrue when ≤ 10,000 ETB — paid out without manual review
amount_minorYes
meets_minimumYes
within_daily_capYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is carried structurally. The description adds non-obvious behavior: 7% default fee unless a custom rate is set, government tax cut from the gross, round-half-up per component, server is authoritative, and the 10,000 ETB auto-pay threshold and 100,000 ETB rolling-24h cap. This is real behavioral context beyond the annotations.

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?

Front-loaded with the one-line purpose, then the fee/tax mechanics and the return summary, then args. Every sentence carries information; mildly dense but nothing extraneous.

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?

An output schema exists so return values needn't be fully enumerated, and the description still summarizes what comes back (breakdown, auto-pay vs. manual, cap). With annotations covering safety, params and mechanics covered, and boundaries stated, an agent has everything needed to call it correctly.

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 coverage is 50%; the description documents amount_minor's meaning (gross santim, minimum 10000), that fee/tax are optional 0–1 overrides representing the account's real rates, and that the fee is cut FROM the gross so the account receives net. It does not describe response_format, leaving that to the schema.

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?

Specific verb+resource ('preview what reaches the destination for a withdrawal') and immediately distinguishes from the mutation siblings jami_get_withdrawal/jami_list_withdrawals by stating it's offline and needs no token. An agent can route to it or away from it without opening the schema.

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?

Explicitly states when to use (preview, no API call, no token) and when not (the authoritative breakdown comes from the real withdrawal). Also fills the critical decision boundary: which amounts auto-pay vs. go to manual review.

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