Skip to main content
Glama
Sign In
Karbon MCP Server

Karbon MCP Server

by Mad-Man-Dan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create client group

create_client_group

Create a client group in Karbon by specifying a name and adding existing contacts or organizations as members, with optional settings for owner, manager, description, and visibility.

Instructions

Create a new client group in Karbon. Members are existing contacts and/or organizations.

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": {
      "FullName": "<FullName>"
    },
    "name": "create_client_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
MembersNo
FullNameYesThe full name of the client group
ClientOwnerNoEmail address of the Karbon user who owns this client relationship
ContactTypeNoContact type label, e.g. 'Client'. Valid values come from get_tenant_settings.
ClientManagerNo
PrimaryContactNoContactKey of the group's main contact
RestrictionLevelNo
EntityDescriptionNoFree-form description of the client group
UserDefinedIdentifierNoYour own external ID for this client group

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Create' (a mutation) but does not disclose auth requirements, side effects, or whether the operation is reversible. The only behavioral clue is that members must be existing, which is minimal.

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 sentences with no fluff. The verb and resource are front-loaded. Every phrase earns its place, clearly stating the action and a key constraint about members.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 9 parameters, nested objects, and no output schema, the description does not mention return values or typical behavior. The agent lacks guidance on what to expect after creation. Annotations are absent, so the description should compensate but falls short.

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?

With 67% schema description coverage, the baseline is 3. The description adds value by specifying that members must be existing contacts/organizations, but does not explain all 9 parameters (e.g., ClientManager lacks description). Overall, marginal improvement over schema.

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 clearly states the verb 'Create' and the resource 'client group' in Karbon. It specifies that members are existing contacts and/or organizations, which distinguishes it from sibling tools like create_contact or create_organization.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for creating groups but does not explicitly state when to use it versus alternatives (e.g., when to use create_client_group vs create_contact). It mentions members are existing, hinting at prerequisites, but no clear guidance on when not to use this tool.

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