Skip to main content
Glama

Bhutan Trips by Druk Asia

Create Member

create_member

Creates a member using contact details. IsActive and Status are always set to true by the API. 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": {
      "email": "<email>",
      "fullname": "<fullname>",
      "phone_country_code": "<phone_country_code>",
      "phone_number": "<phone_number>"
    },
    "name": "create_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesMember email address.
fullnameYesMember full name.
phone_numberYesPhone number, e.g. 17123456.
phone_country_codeYesPhone country code, e.g. +975.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / email / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds genuinely non-obvious behavior: IsActive and Status are always forced to true by the API regardless of what the caller intends, and authentication happens automatically via the x-api-key header. What is still missing is any note on duplicate-email handling or what the call returns.

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 tight sentences, front-loaded with the core action, then the surprising side effect, then the auth note. No filler; the phrase "using contact details" is the only slightly vague wording.

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?

For a four-required-parameter creation tool with no output schema, the definition covers the action and the forced-field behavior but omits what a successful call returns (e.g., a member identifier) and how validation failures or existing emails are handled. It is adequate to invoke, less so to reason about results.

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%, so all four parameters (email, fullname, phone_country_code, phone_number) are already documented, and the description only summarizes them as "contact details." It adds no format or constraint meaning beyond the schema, which is the expected baseline here.

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 gives a specific verb and resource ("Creates a member") plus the input basis ("using contact details"), which clearly separates it from sibling creation tools such as create_booking or create_payment. It does not explicitly call out those siblings, but the resource name alone is sufficiently distinctive.

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 implied by the verb rather than stated: nothing says when a member should be created versus looked up with get_member, or under what business conditions creation is appropriate. The only explicit prerequisite is the API key, so an agent gets context but no exclusions or alternatives.

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