Skip to main content
Glama

create_transfer_payment

Cria o pedido do TRASLADO escolhido e devolve o LINK DE PAGAMENTO (payment_url, Stripe, em USD): o hospede abre o link e paga na pagina segura — NUNCA peca ou digite dados de cartao aqui. So chame DEPOIS de o hospede escolher a cotacao e confirmar preco, trajeto, pickup_at de cada trecho e passageiros (get_transfer_quote), e em ate ~10 min da busca (a cotacao precisa ter ~25 min de validade). Cobra SO em USD, mesmo que o hotel tenha sido em BRL. A reserva so e feita depois do pagamento confirmado: acompanhe com get_activity_order (order_id atv_...); o link vale cerca de 35 min. Cancelamento MANUAL (support@besthotels4.me).

nome, sobrenome, email: do TITULAR. ddi (ex.: '+55') e telefone (so o numero, sem repetir o DDI):
OBRIGATORIOS — o motorista liga para esse numero. ida: objeto com os campos que a cotacao EXIGE no
1o trecho (de get_transfer_quote), ex.: {flight_number, airline, origin_city}; trem: train_number,
origin_city; navio: ship_name; hospedagem: location (quando a ponta e o hotel, o nome do hotel de
`contexto.hotel` da cotacao: nao pergunte ao hospede); `observacoes` (opcional, ate 300 caracteres)
fica so com a NOSSA equipe: NAO vai ao motorista nem ao fornecedor, entao nao use para recado ao
motorista. Limites: flight_number/train_number 20, airline/origin_city/ship_name 60, location 160
(acima disso e recusado). volta: o mesmo para o 2o trecho de uma cotacao 'ida_volta'. Peca ao
hospede, nunca invente: faltando algum, o erro lista quais. locale: 'pt', 'es' ou 'en' (pagina de
pagamento, e-mails e voucher).

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": {
      "token": "<token>",
      "quote_id": "<quote_id>",
      "nome": "<nome>",
      "sobrenome": "<sobrenome>",
      "email": "<email>",
      "ddi": "<ddi>",
      "telefone": "<telefone>"
    },
    "name": "create_transfer_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
ddiYes
idaNo
nomeYes
emailYes
tokenYes
voltaNo
localeNo
quote_idYes
telefoneYes
sobrenomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses that the tool only returns a payment link, that the booking is created only after confirmed payment, that the link expires in ~35 minutes, that charges are always USD, and that sensitive card data must never be entered here. It also warns that `observacoes` never reaches driver or supplier and that missing required fields produce an error listing them. It stops short of describing token/auth expectations or what happens if the link expires.

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, payment-link behavior and expiry are front-loaded before the parameter detail, and nearly every sentence carries operational information. It is dense and long with some run-ons and repeated emphasis (the 'peça ao hóspede, nunca invente' warning appears twice), but the length is largely justified by 10 undocumented parameters.

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?

For a 10-parameter mutation tool with no annotations and no output schema, the definition covers prerequisites, return artifact, expiry, currency, downstream tracking and per-field constraints. The notable gaps are the unexplained `token` parameter and an incomplete picture of how the caller learns the link expired or payment failed.

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 0% (bare titles only), so the description must compensate, and it largely does: it defines `nome`/`sobrenome`/`email` as the holder's, gives `ddi` format ('+55') and `telefone` as digits without the DDI, enumerates required per-mode fields for `ida`/`volta` with examples and length limits, and constrains `locale` to 'pt'/'es'/'en'. It leaves `token` and `quote_id` unexplained, which keeps it from a 5.

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 names a specific action and artifact: it creates the transfer order for the chosen quote and returns a Stripe payment link (`payment_url`) in USD. It clearly separates this from `get_transfer_quote` (the prerequisite) and `get_activity_order` (post-payment tracking), so an agent can distinguish the role without opening any 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?

Explicit preconditions: only call after the guest has chosen the quote and confirmed price, route, each leg's `pickup_at` and passengers via `get_transfer_quote`, and within ~10 minutes of the search. It also states the follow-up path (`get_activity_order` with `order_id atv_...`) and that cancellation is manual via support email, leaving nothing to inference.

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