Skip to main content
Glama

Control Parameter Set

control_parameter_set

Set typed runtime values on the parameter bound to a rendered control, with preview, conflict checks, journaling, read-back, and reversible restore in the same browser session.

Instructions

Set typed runtime values on the parameter bound to a rendered control.

The parameter key is read from the native component and cannot be redirected by the caller. Values use stringValue, numberValue or boolValue wire fields. The action is browser-session-only, previewed, conflict-guarded, journalled, read back and reversible in the same document with operation_restore.

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": {
      "page_id": "<page_id>",
      "component_id": "<component_id>",
      "values": "<values>",
      "expected_interaction_fingerprint": "<expected_interaction_fingerprint>"
    },
    "name": "control_parameter_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes
dry_runNo
page_idYes
report_idNo
component_idYes
expected_interaction_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds real behavioral context beyond that: the write is browser-session-only, previewed, conflict-guarded by a fingerprint, journalled, read back, and reversible in the same document via operation_restore. It also discloses that the parameter key is derived from the native component and cannot be overridden, which is a genuine calling constraint. This is substantial disclosure that the annotations do not carry.

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?

Three short sentences, front-loaded with the action and its scope, then constraints, then safety properties. Dense but every sentence carries information; 'journalled' and 'read back' are slightly jargon-heavy but not wasteful.

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?

An output schema exists, so return values need not be described, and the mutation/reversibility profile is well covered. However, for a 6-parameter mutation with 0% schema coverage, leaving dry_run and the identifier parameters unexplained is a real completeness gap that an agent must resolve from types alone.

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

Parameters2/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 carry parameter meaning, and it only covers part of it. It explains that values use stringValue/numberValue/boolValue wire fields and that no parameter-key argument exists, and 'conflict-guarded' hints at expected_interaction_fingerprint. It says nothing about page_id, component_id, report_id, or that dry_run defaults to true, which is arguably the most consequential parameter given the tool defaults to preview.

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: 'Set typed runtime values on the parameter bound to a rendered control.' That is materially clearer than a tautology and distinguishes it from pure control setters by scoping it to parameter values. It stops short of naming the control_*_set siblings it might be confused with, so sibling differentiation is implied rather than stated.

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 description gives an implicit routing hint by naming operation_restore as the undo path and by noting the parameter key cannot be redirected by the caller (so no need to hunt for a key argument). It never states when to use this versus control_checkbox_set / control_filter_set, nor any prerequisites for the interaction fingerprint. Usage is inferable but not spelled out.

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

Deploy Server

Other Tools