Skip to main content
Glama

Check your merchant checkout and booking

get_direct_payment
Idempotent

Check an existing deposit booking on your signed-in Direct account: reconcile its Stripe Checkout payment and return its receipt and the separate booking state. Use it after send_to_business returned a payment_url for a deposit booking, to see whether the person has paid; it cannot start a payment, which the person makes on Stripe’s hosted page. Pass biz (the business id from its card) and task_id (the task id send_to_business returned for that booking). Requires direct:tasks. Uses only the stored merchant account and amount and creates no new charge or booking identity; a verified paid checkout may finish its already-authorized held booking. Payout status remains unknown: paid does not mean a bank payout. Safe to repeat. For owner_record_pending, check again to finish saving the owner’s booking record. owner_notice_unconfirmed means delivery is unverified and checking again will not resend it. appointment_state=cancelled records a later cancellation. Example: biz='harbor-plumbing', task_id='tk_5d0' after send_to_business returned a payment_url for a deposit booking.

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": {
      "biz": "<biz>",
      "task_id": "<task_id>"
    },
    "name": "get_direct_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bizYesThe business id (from its card) the deposit booking was made with.
task_idYesThe task id send_to_business returned for that booking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / biz / description
      Added value: +"The business id (from its card) the deposit booking was made with."
    • addedInput schema / properties / task_id / description
      Added value: +"The task id send_to_business returned for that booking."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the required direct:tasks scope, that it uses only the stored merchant account and amount, creates no new charge or booking identity, that a verified paid checkout may finish its already-authorized held booking (consistent with readOnlyHint=false), and that paid does not imply a bank payout. It also says 'Safe to repeat' reinforcing idempotentHint=true, and enumerates boundary states (owner_record_pending, owner_notice_unconfirmed, appointment_state=cancelled).

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 purpose, then usage, then parameter binding, then edge cases and example — a sensible order. It is dense and long for a two-parameter tool, and the cluster of state names is slightly heavy, but nearly every sentence carries operational value.

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, yet the description explains what comes back (receipt plus separate booking state) and flags that payout status remains unknown. With auth scope, mutation caveat, repeatability, and edge states all covered, nothing material is missing for correct invocation.

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 100%, so the schema already documents both parameters and baseline is 3. The description adds relational meaning beyond the schema: biz comes 'from its card' and task_id is 'the task id send_to_business returned for that booking,' plus a concrete example (biz='harbor-plumbing', task_id='tk_5d0').

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 and resource: 'Check an existing deposit booking... reconcile its Stripe Checkout payment and return its receipt and the separate booking state.' It explicitly contrasts with send_to_business by stating 'it cannot start a payment, which the person makes on Stripe's hosted page,' so an agent can distinguish the two without opening schemas.

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?

States the precise trigger: 'Use it after send_to_business returned a payment_url for a deposit booking, to see whether the person has paid.' It names the exclusions (cannot start a payment) and the follow-up conditions (check again for owner_record_pending; checking again will not resend for owner_notice_unconfirmed).

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