Skip to main content
Glama

Create a client

clipember_create_client

Create a client (a brand or customer the user manages) to group their social accounts. Names are unique per user, ignoring case. Add accounts afterwards with clipember_set_account_client.

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": "clipember_create_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesClient name, e.g. the brand name
colorNoLabel color as #rrggbb; picked automatically if omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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, so the safety profile is covered. The description adds a genuine behavioral constraint not present in structured fields: names are unique per user, case-insensitively, implying duplicate creation fails. It stops short of saying what the call returns or how a duplicate-name failure surfaces.

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, no redundancy, and the core purpose is front-loaded before the follow-up hint. Every clause carries information: definition, uniqueness rule, next step.

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 two-parameter creation tool with no output schema, the description covers purpose, resource definition, uniqueness constraint, and the follow-up tool. It is nearly complete, lacking only a note on what is returned (e.g. the new client ID) or how duplicate-name errors are surfaced.

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 100%, so the baseline is 3, but the description adds semantics the schema lacks: the uniqueness and case-insensitivity rule that governs what value of `name` will succeed. The `color` auto-pick behavior is already documented in the schema, so nothing extra is contributed there.

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 client") and then defines the domain object parenthetically as "a brand or customer the user manages" that groups social accounts. That definition lets an agent distinguish it from sibling tools like clipember_create_tag or clipember_update_client without opening a schema.

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 explicitly sequences the workflow: "Add accounts afterwards with clipember_set_account_client," which names a real sibling and the condition under which to call it. It does not state when-not to use this tool (e.g. use update_client for existing clients), so it falls just short of full routing guidance.

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