Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Archive Custom Field Group

archive_custom_field_group

Archives a custom field group by ID to retire unused field groups; requires Custom Fields Admin or Global Admin permissions.

Instructions

Archive 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": "archive_custom_field_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does add genuine value by naming the required role, which is auth context structured fields do not supply. However, it says nothing about whether archiving is reversible, what happens to fields inside the group, or whether the group must be unused — key facts for a mutating operation.

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, zero filler, with the action stated first and the permission requirement immediately after. Nothing could be removed without losing information.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the one parameter is fully documented. What is missing is the consequence of the call — reversibility and effect on contained fields — which matters for an unannotated mutation tool and would need only a clause to fix.

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% and the single parameter's schema text already explains it comes from list_custom_field_groups. The description adds no format, sourcing, or constraint detail beyond that, so the baseline of 3 applies.

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: 'Archive a custom field group'. The word 'group' distinguishes it from archive_custom_field, but the description never explicitly contrasts the two siblings, so the differentiation is implicit rather than stated.

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 permission prerequisite ('Requires the Custom Fields Admin role (or Global Admin)') gives an agent a deployment-time condition, but there is no guidance on when to archive versus update or delete, and no mention of what precondition must hold (e.g. group must be empty).

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