Skip to main content
Glama

Bhutan Trips by Druk Asia

Get Payment Status

get_payment_status
Read-only

Checks whether a booking's payment has succeeded. Requires a valid Druk Asia API key (sent automatically via the x-api-key header).

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": {
      "online_booking_id": "<online_booking_id>"
    },
    "name": "get_payment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
online_booking_idYesOnlineBookings.Id (booking_id from create_booking).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / online_booking_id / minLength
      Removed value: -1
    • addedInput schema / properties / online_booking_id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,64}$"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful non-annotation context: a Druk Asia API key is required and is transmitted automatically via the x-api-key header. However, it says nothing about what the check returns (pending vs succeeded vs failed) or rate/polling behavior, which matters most for a status-checking tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, the purpose is front-loaded, and the auth note follows immediately. No padding or restated title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of explaining the returned status values and should say more than it does. Auth requirements are covered, but an agent still doesn't know what a 'payment status' response looks like or whether polling is appropriate.

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 coverage is 100% – the single parameter online_booking_id is documented in the schema with a pattern and an explicit link to create_booking. The description adds no syntax or sourcing detail beyond that, so the baseline of 3 applies.

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?

The description states a specific verb and resource: 'Checks whether a booking's payment has succeeded.' An agent can tell this is a read of payment status, but there is no explicit differentiation from siblings such as create_payment or get_booking, which an agent might plausibly reach for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the purpose statement – an agent infers it should be called to verify a booking's payment state after checkout. There is no explicit when-to-use condition (e.g., polling after create_payment) and no stated alternatives or 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.

Resources