Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Update Custom Field Group

update_custom_field_group

Renames a custom field group by ID and new name; requires the Custom Fields Admin or Global Admin role.

Instructions

Rename a custom field group. 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": {
      "custom_field_group_id": "<custom_field_group_id>",
      "name": "<name>"
    },
    "name": "update_custom_field_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name.
custom_field_group_idYesThe ID of the group (from list_custom_field_groups).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It usefully names the required role, but says nothing about whether the rename is reversible, whether the previous name is preserved anywhere, or whether it affects fields inside the group — the behaviors an agent most needs before mutating a shared resource.

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 short sentences, action first and constraint second, with no filler. Every sentence carries information an agent needs.

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 simple two-parameter mutation with an output schema and full schema coverage, the description covers the action and the authorization requirement adequately. The main remaining gap is the absence of any statement about side effects or reversibility on a rename.

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 coverage is 100%, so both parameters are already documented in the input schema, including that the ID comes from list_custom_field_groups. The description's "Rename" wording confirms that only the name changes and the group is otherwise untouched, which is a small but real addition above the schema.

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?

"Rename a custom field group" states a specific verb and resource, and the verb choice inherently separates it from create_custom_field_group and archive_custom_field_group. It stops short of naming a sibling to route against, but the operation is unambiguous.

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 prerequisite (Custom Fields Admin or Global Admin role) gives an agent a real precondition for calling it, which is implied guidance toward use. However, there is no explicit statement of when to choose this over archive or create, nor any note about what scope the rename applies to.

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