Skip to main content
Glama

Quote an AI service invoice

quote_invoice
Read-onlyIdempotent

Answers what a specific OpenRouter top-up or other AI service invoice charges, whether it can still be paid through Rozo Checkout, and which coins can pay it. Takes the payment link URL and returns the merchant, invoice amount, callerPays (the total USD charged: invoice plus the Rozo service fee; also callerPaysAtomicUsdc in 6-decimal units), the breakdown original (invoice face value), serviceFee and feeBps (fee rate in basis points, 100 = 1%), the link expiry, payability and supportedSources: the coins THIS invoice can be paid with. The exact amount to send in a given coin, which adds bridge and network fees, or the FX spread on a native coin, on top of callerPays, comes from create_deposit_order. Offer a native coin (ETH, BNB, POL, SOL) only when it appears in supportedSources. Creates nothing and moves no funds.

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": {
      "url": "<url>"
    },
    "name": "quote_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPayment link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_...

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Coinbase link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_..."New value: +"Payment link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_..."
  2. First observed

TDQS

A4.4/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 reinforces that with 'Creates nothing and moves no funds'. More importantly it discloses semantics annotations cannot: what callerPays means versus original and serviceFee, that feeBps is basis points (100 = 1%), that callerPaysAtomicUsdc is 6-decimal, and that payability/expiry are returned.

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?

The purpose and the sibling hand-off are front-loaded, and every clause carries information — the return-field glossary and the native-coin rule are both load-bearing. It is a long run-on paragraph with heavy parentheticals, which hurts scanability, but there is no filler.

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?

There is no output schema, so the description must describe the response, and it does so field by field (merchant, amount, callerPays, callerPaysAtomicUsdc, original, serviceFee, feeBps, expiry, payability, supportedSources). For a single-parameter read-only quote tool, nothing an agent needs before calling it is missing.

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% and the url property already spells out the accepted Coinbase payment-link and payment-session URL formats. The description only restates 'Takes the payment link URL', adding no constraints (e.g. that the link must be a Rozo/Coinbase link or what happens with an unrecognized URL), so the baseline of 3 applies.

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?

The description opens with a specific triple purpose: what a given OpenRouter top-up or other AI service invoice charges, whether it is still payable through Rozo Checkout, and which coins can pay it. It is clearly distinguished from create_deposit_order, which is named as the tool that computes the exact amount to send in a given coin.

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?

It routes the agent explicitly to create_deposit_order for the exact coin-denominated send amount including bridge/network fees and FX spread, and gives a conditional rule: offer a native coin (ETH, BNB, POL, SOL) only when it appears in supportedSources. It does not state when this tool itself should be skipped (e.g. for non-Rozo-payable or expired links), so it falls short of explicit 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.