Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

List Custom Fields

list_custom_fields

Retrieve available custom fields to discover fields that may lack values, filtered by task, runbook, or all scopes and optionally by workspace.

Instructions

List all available custom fields to discover fields that may not have values yet.

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

Input Schema

NameRequiredDescriptionDefault
scopeNoWhich custom fields to return: "task" for task-level fields only, "runbook" for runbook-level fields only, or "all" (default) for fields of every scope except the deprecated runbook_end scope and project-level scopes, which are never returned. The runbook scope includes the dashboard fields on the runbook homepage (e.g. Executive summary, Additional notes), the Post-Implementation Review (PIR) and the Incident Review (e.g. Incident Summary, RCA, Lessons Learned), all of which are set with update_runbook.all
workspace_idNoOptional workspace ID to filter custom fields. If not provided, returns fields from all accessible workspaces.
include_globalNoWhen workspace_id is provided, also include globally available (shared) custom fields alongside the workspace's own. Set to False to return only workspace-specific fields.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. 'List all available' implies a non-mutating, exhaustive read, but it never states that explicitly and says nothing about pagination or scoping caveats (the deprecated runbook_end exclusion lives only in the schema). An output schema exists, which relieves it of describing return values.

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?

One short sentence with the purpose front-loaded and no filler. It is arguably under-specified rather than bloated, but every word earns its place.

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?

With 100% schema coverage and an output schema, the structured data covers parameters and returns. However, for a tool with three optional filtering parameters and multiple sibling list tools, the description does not mention scoping of results or how to choose this over related list tools, leaving a modest gap.

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 the schema already documents scope, workspace_id, and include_global thoroughly. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the work.

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 ('List all available custom fields'), which is clearly distinct from the sibling 'list_custom_field_groups' by resource name. It does not explicitly say how it differs from other list_* tools, keeping it below a 5.

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 phrase 'to discover fields that may not have values yet' implies a discovery use case, giving some when-to-use signal. It offers no exclusions or named alternatives, so guidance remains implied rather than explicit.

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