Skip to main content
Glama

Add a client

create_client
Idempotent

Use this when the user says a client is new and asks to add them, or an invoice or quote needs a client that list_clients does not find. Adds a client (name and optional 15-digit UAE TRN, checked as check_trn does) to the business and returns its client_id. If a client with the same TRN or exactly the same name exists, that client is returned and nothing is created. Do not use it for a client that already exists (list_clients).

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>"
    },
    "name": "create_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
trnNo
nameYes
business_idNoFrom list_businesses. May be left out when the connection shares exactly one business.
client_typeNobusiness or individual.
idempotency_keyNoOptional. A unique string (for example a UUID) for this request: a retry with the same key returns the first result instead of writing again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 by disclosing the duplicate-handling rule: if a client with the same TRN or the exact same name exists, that client is returned and nothing is created. It also states the TRN is validated the way check_trn validates and that the response carries client_id, which is exactly the mutation-side context an agent needs before writing.

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 sentences, front-loaded with the trigger and no padding, all of which carry real information. The closing 'Do not use it for a client that already exists (list_clients)' re-states the dedupe behavior from the previous sentence, though from an agent-routing angle, so the slight redundancy is defensible.

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?

For a create tool with no output schema, the description covers the return value (client_id), the dedupe/no-op case, and the TRN validation rule, which are the things an agent cannot learn from the schema or annotations. Nothing material is missing for a correct call.

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 60%, so the baseline would be a 3; the description compensates by constraining the trn parameter to a 15-digit UAE TRN (tighter than the schema's maxLength 40) and by clarifying that name is the identifying field used for dedupe. business_id, client_type and idempotency_key are left to their schema descriptions, which do carry text.

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?

States a specific verb and resource ('Adds a client ... to the business') and names the return value (client_id). It also distinguishes itself from the siblings it could be confused with, calling out list_clients for lookup and check_trn for validation.

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?

Gives explicit trigger conditions ('user says a client is new and asks to add them, or an invoice or quote needs a client that list_clients does not find') and an explicit exclusion ('Do not use it for a client that already exists (list_clients)'). The agent has both the when and the when-not, with the alternative named.

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