Workspace369

Add client custom fields

client_custom_fields_create

DestructiveIdempotent

Define custom fields on client records (text, select, boolean, number, date; at most 30 per call). A key that already exists with the same type is kept unchanged, so repeating a call is safe; a different type is refused and nothing is deleted. Afterwards clients_create and clients_update accept values by key. Use crm_apply_blueprint to add stages and fields together. Needs permission to edit business details.

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": {
      "fields": "<fields>"
    },
    "name": "client_custom_fields_create"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	Yes	Custom fields to add, at most 30. A field whose key already exists with the same type is left as it is.
`dry_run`	No	True previews the result and writes nothing. Default false.

Output Schema

Name	Required	Description
`counts`	Yes
`stages`	Yes
`applied`	Yes	True when the changes were written.
`dry_run`	Yes	True when nothing was written.
`warnings`	Yes
`custom_fields`	Yes
`default_stages_added`	Yes	True when the five default stages were written first because the workspace had none stored.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes well beyond the annotations: discloses the 30-field cap, the idempotent same-key/same-type behavior, and the refusal semantics when a type differs ('nothing is deleted'). This meaningfully softens the alarming destructiveHint=true, though it never explicitly reconciles that mismatch, which keeps it from a 5.

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?

Four tight sentences, front-loaded with the core action, then idempotency behavior, then the alternative tool and permission requirement. Every sentence contributes a distinct fact with no filler.

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 two-parameter mutation tool with full schema coverage and an output schema, nothing an agent needs is missing: limits, idempotency, refusal behavior, prerequisite permission, sibling alternative, and downstream consumers are all covered.

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 key, type, options, sortable/filterable/searchable and dry_run are already documented in the schema. The description only restates the array-level 30-item cap and idempotency note, adding little syntax or format detail beyond the structured fields.

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 ('Define custom fields on client records') and enumerates the supported field types, which immediately separates it from client_stages_create and crm_apply_blueprint. An agent can identify the operation without opening the schema.

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?

Explicitly names the alternative ('Use crm_apply_blueprint to add stages and fields together') and the condition that selects it, plus states the prerequisite permission ('Needs permission to edit business details'). It also describes the downstream payoff (clients_create/clients_update accept values by key), so the agent knows the follow-up step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Workspace369 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.