Skip to main content
Glama

Create client

crunch_create_client

Create a client for invoicing by providing a name and billing address; check existing clients first to avoid duplicates.

Instructions

Create a client (customer) to invoice. A name and a billing address with line1, line2 and country are needed. Check crunch_list_clients first to avoid duplicates.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCustomer name, for example Example Customer Ltd
noteNoInternal note about the customer
emailNoEmail address invoices are sent to
extraNoAdditional raw fields for the request body, using Crunch's own field names (advanced). Merged last.
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
billing_addressYesBilling address
payment_terms_daysNoDefault payment terms in days, for example 30

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the write/read nature needs no restatement. The description adds useful operational context — required address fields and a duplicate-avoidance workflow — but says nothing about non-idempotency, what is returned on success, or the dry_run preview path.

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, front-loaded with purpose and followed by the constraint and the prerequisite check. Every sentence carries distinct information; nothing is redundant padding.

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 create tool with full schema coverage and safety annotations, the description covers purpose, minimum required inputs, and the duplicate-check precondition. It omits the dry_run preview affordance and any indication of the return value, which are minor given there is no output schema to lean on.

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%, including nested field docs for billing_address, so the schema carries the parameter burden and a baseline 3 applies. The description only restates which required fields exist and does not add meaning for dry_run, extra, note, email, or payment_terms_days.

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 definition opens with a specific verb and resource, 'Create a client (customer) to invoice,' and even glosses 'client' as 'customer' so the domain term is unambiguous. It is clearly distinguishable from read-oriented siblings such as crunch_list_clients and crunch_get_client.

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 gives an explicit pre-flight step: 'Check crunch_list_clients first to avoid duplicates,' naming the concrete alternative to call first. There is no when-not guidance (e.g. when to use update_client instead), so it stops 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.

Deploy Server

Other Tools