Skip to main content
Glama

Control Filter Set

control_filter_set

Set the runtime condition or values of a rendered dimension filter control by building the filter on its actual concept and validating it against the native schema before a previewed, journalled write.

Instructions

Set the runtime condition/value of a rendered dimension filter control.

Supports non-parameter list/input/advanced/slider presets through the native canvas-control editor. The saved bound concept is immutable here: the tool builds the filter on the control's actual concept and validates it against the native condition/schema contract. Get the interaction fingerprint from component_interaction_state. Browser-session state only; preview by default, journalled dispatch/read-back, and operation_restore while the document lives. Checkbox has a stricter dedicated tool; parameters and Analysis are rejected.

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>",
      "value": "<value>",
      "expected_interaction_fingerprint": "<expected_interaction_fingerprint>"
    },
    "name": "control_filter_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
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

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes well beyond that by disclosing that state is browser-session-scoped and ephemeral, that dispatch is previewed by default and journalled, that operation_restore is available while the document lives, and that the saved bound concept is immutable. The one residual gap is the return/read-back shape, which the output schema presumably covers.

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 sentence, followed by scope, invariants, prerequisite, and exclusions in a logical order with no filler. Some phrasing is dense domain jargon ('journalled dispatch/read-back', 'native condition/schema contract') that costs a little readability but does carry 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 annotations and an output schema present, the definition covers scope, safety, prerequisites, exclusions, and reversibility well. What keeps it from 5 is the unexplained parameter surface — an agent still has to infer the value payload shape and the role of page_id/report_id purely from the schema.

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% across 6 parameters, so the description carries the burden and only partially meets it: it points to component_interaction_state for expected_interaction_fingerprint and implies dry_run via 'preview by default'. The nested value object (condition, include, number_values, string_values) and page_id/report_id are left entirely to the raw schema, so the added meaning is real but incomplete.

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?

Uses a specific verb ('Set') plus a precisely scoped resource ('runtime condition/value of a rendered dimension filter control') and immediately bounds the supported control presets (non-parameter list/input/advanced/slider). It also names the excluded case (Checkbox has a dedicated tool) and the rejected domains (parameters, Analysis), so an agent can distinguish it from control_checkbox_set and control_parameter_set without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states the when-not cases ('Checkbox has a stricter dedicated tool; parameters and Analysis are rejected') and the prerequisite workflow ('Get the interaction fingerprint from component_interaction_state'). It also flags the default mode stack (preview by default, journalled dispatch/read-back, operation_restore), which is exactly the context needed to choose this tool correctly.

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