Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

List Custom Field Groups

list_custom_field_groups

List custom field groups to see which section each custom field appears in. Archived groups are excluded, so results reflect only active groups.

Instructions

List custom field groups, which control the section a custom field is shown in. Archived groups are not returned; the API does not list them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_custom_field_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does disclose one genuinely useful trait: archived groups are omitted and the API cannot return them, which prevents an agent from hunting for missing groups. It does not address read-only safety, ordering, permissions, or scope (workspace vs global), which matter given the sibling set is workspace-oriented.

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, front-loaded with the core action, and the second sentence earns its place by adding non-obvious exclusion behavior. There is no redundant restatement of the title or filler wording.

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 zero-parameter list tool with an output schema, the description covers purpose plus the one surprising behavior (archived groups excluded), which is close to sufficient. The remaining gap is scope/authorization context — whether results are global or tied to a workspace — which is not addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly avoids wasting words on parameter semantics.

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?

The description gives a specific verb and resource ("List custom field groups") and even explains what the resource is semantically ("control the section a custom field is shown in"), so an agent understands the entity being enumerated. It stops short of explicitly differentiating itself from the closely related sibling list_custom_fields, leaving that distinction to be inferred from names alone.

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?

Usage is only implied: an agent can reason that this is the way to discover group containers before listing or creating custom fields, but the description never states when to call it versus list_custom_fields or get_custom_field. No exclusions or prerequisites are given.

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