Onplana

create_custom_field_def

Create a custom field definition (PRO+ feature). fieldType: one of TEXT, TEXTAREA, NUMBER, DATE, DROPDOWN, MULTI_SELECT, CHECKBOX, URL, EMAIL, PHONE, CURRENCY, RATING. entityType: PROJECT, TASK, or PROPOSAL. DROPDOWN/MULTI_SELECT require at least one option. Omit projectId for an org-wide field (admin/manager only). Set projectId to scope the field to one project (project owner/manager allowed).

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": {
      "name": "<name>",
      "fieldType": "<fieldType>",
      "entityType": "<entityType>"
    },
    "name": "create_custom_field_def"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	1-100 chars.
`options`	No	Required for DROPDOWN/MULTI_SELECT.
`required`	No	Whether this field is mandatory.
`fieldType`	Yes
`projectId`	No	Scope to one project. Null or omit for org-wide.
`entityType`	Yes
`description`	No	Optional field description.
`defaultValue`	No	Optional default value.

Schema Changelog

Changes observed during successful MCP inspections.

AddedJun 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false), so the bar is lower, and the description adds real context the annotations lack: the PRO+ feature gate and the differing authorization rules for org-wide (admin/manager) vs project-scoped (project owner/manager) fields. It still omits return behavior and uniqueness constraints.

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?

Purpose is front-loaded in the first clause and the remaining sentences are dense with constraints and no filler. Slightly enumeration-heavy, but every sentence carries operational information.

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 mutation tool with no output schema, the description covers the key domain constraints (tier, valid types, option requirement, scoping and authorization). It is nearly complete, missing only what happens on success or on a name collision.

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 75%, so the baseline is 3. The description largely restates what the schema already encodes — the fieldType/entityType enumerations and the option requirement for DROPDOWN/MULTI_SELECT — adding only the role implications of projectId rather than new syntax or format meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Create') and resource ('custom field definition') and immediately scopes it with the PRO+ tier gate. It is unambiguous against siblings like update_custom_field_def, list_custom_field_defs, and set_custom_field_value.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete selection guidance for the projectId parameter (omit for org-wide vs set to scope to one project) and ties each path to an allowed role. It does not explicitly name the sibling to use for editing or listing, so it falls short of full when/when-not routing.

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

All Onplana tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.