Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Get Custom Field

get_custom_field

Retrieve a custom field's metadata, including its type and valid options, by providing its ID to understand available values before use.

Instructions

Get a custom field's metadata including its type and valid options.

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_id": "<custom_field_id>"
    },
    "name": "get_custom_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
custom_field_idYesThe ID of the custom field to retrieve.

Output Schema

NameRequiredDescriptionDefault

No arguments

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 must carry the behavioral burden. 'Get' plus 'metadata' implies a safe read, and it discloses that the payload includes type and valid options, but it says nothing about permissions, error handling for a stale/deleted ID, or whether option lists are paginated. An output schema exists, so return shape need not be restated.

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?

A single well-formed sentence that leads with the action and enumerates the most useful returned content. Nothing is wasted, though it is terse enough to feel like a label rather than a guide.

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?

For a one-parameter read tool with an output schema, the essentials are covered. However, it omits how to obtain a valid ID and what happens on a missing/deleted field, which are the main failure modes an agent would encounter.

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 description coverage is 100%, so the single custom_field_id parameter is already fully documented in the schema. The description adds no format hints (e.g., where IDs come from) beyond the schema's own text, making the baseline 3 appropriate.

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 ('Get a custom field's metadata') and names the contents (type, valid options), so an agent knows exactly what it returns. It does not explicitly distinguish itself from list_custom_fields, leaving that differentiation to inference.

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: the required single ID suggests fetching one known field, contrasting implicitly with listing tools. There is no explicit when-to-use guidance, no mention of using list_custom_fields first to discover IDs, and no note on behavior for unknown IDs.

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