Skip to main content
Glama

Register customer

register_customer
Destructive

Register as a GYOTAK customer. Collect name, phone, address, email, and customer type (Retail or Wholesale) via conversation BEFORE calling this tool. Returns a customerKey for future orders.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "address": "<address>",
      "customerType": "<customerType>"
    },
    "name": "register_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name (English)
emailNoEmail address (optional)
phoneYesContact phone number
addressYesShipping address
customerTypeYesCustomer type: Retail (consumer) or Wholesale (business)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the description needn't re-establish safety. What it does add is the return value (customerKey) and the pre-call data collection step. It fails to explain the practical consequence of the annotations – that a repeat call creates a duplicate customer rather than updating one – which is the single most useful behavioral fact here.

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 sentences, both carrying load: the first names the operation and its return, the second gives the ordering constraint. The prerequisite is front-loaded and nothing is padded.

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 five-parameter creation tool with no output schema, the description covers purpose, prerequisite, and return value, which is most of what an agent needs. The remaining gap is the duplicate/irreversibility risk implied by non-idempotent and destructive annotations, which is left unstated.

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 five parameters, including the Retail/Wholesale enum, are already documented. The description only restates the field list, adding no format, validation, or edge-case meaning beyond the schema. Baseline 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?

"Register as a GYOTAK customer" gives a specific verb and resource, and the description adds the concrete outcome (returns a customerKey for future orders). It is clearly distinguishable from siblings such as recover_customer_key, though it never names an alternative explicitly.

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 states a real precondition: gather name, phone, address, email, and customer type through conversation BEFORE calling, which tells the agent not to call it prematurely. It stops short of naming when-not-to-use or pointing at recover_customer_key for existing customers.

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