Skip to main content
Glama
doricomcp

doricomcp

by kulbiq

dialog_set

Set Dorico dialog controls by title, label, or path: toggle checkboxes and radio buttons, enter text, or choose pop-up/combo box items by name.

Instructions

Set a control in a Dorico dialog: a checkbox or radio button to true/false, a text field to text, a pop-up or combo box to one of its items (by name). control: its title, the label before it, or its path.

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": {
      "control": "<control>",
      "value": "<value>"
    },
    "name": "dialog_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
dialogNo
controlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully explains how the value is interpreted per control type: checkbox/radio to true/false, text field to text, and pop-up/combo to an item name. However, it omits preconditions such as whether the dialog must already be open and what happens on invalid control names or 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?

The description is compact and front-loaded: the core action and value semantics come first, followed by control-locator forms. Every sentence contributes useful information, with only minor density from packing multiple control types into one sentence.

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 three-parameter UI automation tool with no annotations or output schema, the description covers the main interaction semantics well. It is incomplete regarding the 'dialog' parameter and does not state whether a dialog must be open, how errors are surfaced, or what the tool returns.

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 0%, so the description must compensate. It adds meaningful semantics for 'control' by explaining it can be a title, the label before the control, or a path, and it explains 'value' via the control-type mapping. The 'dialog' parameter remains entirely unexplained, leaving a notable gap.

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 states a specific verb and resource: 'Set a control in a Dorico dialog,' and enumerates control types (checkbox, radio button, text field, pop-up, combo box). It is clearly distinguishable from dialog_click by focusing on setting a control's value rather than clicking, though it does not name that sibling explicitly.

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 implied: use this when a Dorico dialog is open and a control must be assigned a value. There is no explicit when-to-use versus when-not guidance, no named alternative such as dialog_click, and no stated prerequisites.

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