Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Create Custom Field Group

create_custom_field_group

Create a reusable custom field group in Cutover after checking existing groups; requires Custom Fields Admin or Global Admin role.

Instructions

Create a custom field group. Groups are shared across the instance. Check list_custom_field_groups first so an existing group is reused. Requires the Custom Fields Admin role (or Global Admin).

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_custom_field_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe group's name.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses the instance-wide sharing scope (a side effect beyond the caller's context), the required Custom Fields Admin or Global Admin role, and a duplicate-avoidance workflow. It stops short of saying what happens if a same-named group already exists (error vs. no-op) and whether the operation is idempotent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the action front-loaded and the prerequisite following logically. No filler, though the role requirement might read more naturally combined with the prerequisite sentence rather than trailing it.

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?

Auth requirements, sharing scope, and dedup guidance cover most of what matters for a one-parameter creation tool, and an output schema exists so return values need not be described. Missing only the collision/duplicate-name behavior, which is the one remaining question an agent would have given the 'check first' instruction.

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?

There is a single parameter with 100% schema description coverage, so the schema carries the semantics and baseline is 3. The description adds no constraint on the name (uniqueness, length, case sensitivity) beyond what the schema already states.

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 custom field group') that an agent can map directly to the action. It implicitly separates itself from create_custom_field via the 'group' object, but does not explicitly contrast with the field-level create sibling, so sibling differentiation is only partial.

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?

Gives an explicit precondition ('Check list_custom_field_groups first so an existing group is reused') naming the sibling to call and the condition that selects it. It also states the role requirement up front, leaving nothing about when/when-not to infer.

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