Skip to main content
Glama

create_client

Create a client so invoices can be billed to them. Returns the new client with its id. Name is required; email is needed later for send_invoice.

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
nameYes
emailNo
phoneNo
taxIdNo
taxExemptNo
billingAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the return shape (new client with id) and the required field, which is useful. But it says nothing about duplicate-name handling, permissions/auth needs, or whether the create is idempotent — meaningful gaps for a mutation tool.

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?

Three short sentences, zero filler, with purpose and return value front-loaded ahead of the parameter notes. Every sentence carries distinct information.

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 6-parameter mutation tool with no annotations and no output schema, the description covers the essential call path and states the return value, so an agent can invoke it correctly with just a name. However, half the parameters remain semantically opaque, which is a real completeness gap given the absent schema documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, so the description must compensate and largely does not. It explains name (required) and email (needed for send_invoice) but leaves phone, taxId, taxExempt, and billingAddress entirely undefined in both schema and prose.

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?

States a specific verb and resource ("Create a client") plus the business reason ("so invoices can be billed to them") and the return value ("the new client with its id"). It is clearly distinguishable from siblings like list_clients or send_invoice, 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?

Gives clear context for when to reach for this tool (before billing invoices) and a forward-looking dependency: email is "needed later for send_invoice," which routes the agent across tools. It lacks any explicit when-not guidance, e.g. what to do if the client may already exist.

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