Skip to main content
Glama

Create customer

create_customer
Destructive

Platforms sending for other businesses: create a customer to attribute numbers, messages and usage to.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe customer's name
metadataNoUp to 50 string values
external_idNoYour id for them; unique per account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"The customer's name"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already disclose readOnly=false, destructive=true, idempotent=false, and openWorld=false, so the description does not need to carry the safety profile. It adds domain context about platforms sending for other businesses, but does not add operational details such as irreversibility, permission requirements, or creation side effects.

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?

The description is a single front-loaded sentence with no redundant or filler content. Every phrase contributes either audience scope or attribution purpose.

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?

Given the simple three-parameter schema, full schema coverage, and rich annotations, the description is nearly complete for calling the tool. It could add one note about creation side effects or return behavior, but the structured fields already cover most operational context.

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 the schema already documents name, metadata, and external_id. The description adds no parameter-level meaning beyond that baseline, which is acceptable when schema coverage is this high.

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 gives a specific verb and resource ('create a customer') and explains the domain purpose: attributing numbers, messages, and usage. It is clearly distinguishable from get/update/delete/list customer siblings.

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 the intended audience ('platforms sending for other businesses') and the reason to create a customer, which gives clear usage context. It does not explicitly name when not to use it or point to alternatives, but the context is strong.

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.