Skip to main content
Glama

Receive quote

get_receive_quote
Read-onlyIdempotent

Estimates how many US dollars arrive in a Poplin account when someone pays to its account details in another currency, with the rate, the fees and the limits on the payment, for personal and business accounts at standard pricing. Use it when someone asks what they would receive for a payment in a currency such as EUR or GBP. It is an estimate; the final terms are shown in the Poplin app.

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": {
      "currency": "<currency>",
      "amount": "<amount>"
    },
    "name": "get_receive_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds real value beyond that by scoping it to personal and business accounts at standard pricing and warning that the figure is an estimate with final terms in the app, though it says nothing about rate freshness or caching.

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?

Three sentences, front-loaded with what is computed and followed by when to use it and the estimate caveat. No filler, though the final caveat sentence could be folded into the first.

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 helpfully enumerates the returned components (amount received, rate, fees, limits) and the estimate disclaimer. Only the amount/currency denomination relationship, a key input question for a 2-param tool, is left ambiguous.

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 0%, so the description must carry the two parameters. It implies currency is the payment currency (EUR, GBP) but never states which currency amount is denominated in, nor any format or bounds beyond the schema's 3-letter pattern and 40-char cap.

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 (estimates) and resource (USD received into a Poplin account from a foreign-currency payment), plus what the result contains: rate, fees, limits. The receiving direction is clear enough to separate it from a send-side quote, but no sibling is named explicitly.

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?

Gives a concrete trigger: 'Use it when someone asks what they would receive for a payment in a currency such as EUR or GBP,' with examples. It does not state when to prefer get_send_quote or get_stablecoin_transfer_quote instead, so the routing guidance is contextual rather than 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.