Skip to main content
Glama

Control Reset

control_reset

Resets a rendered filter, parameter, or date control to its saved default via an addressable reset, requiring a current interaction fingerprint; browser-session state only.

Instructions

Reset a rendered filter, parameter or date control to its saved default.

Uses stateActionService's addressable reset, not a page-wide reset or DOM keystrokes. Requires a current interaction fingerprint. Browser-session state only; dispatch is journalled and read back, and operation_restore can restore the pre-reset runtime value while the same browser document remains alive.

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

Input Schema

NameRequiredDescriptionDefault
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
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses the mechanism (addressable reset), the lifetime of the change (browser-session state only, restorable while the same document is alive), and the journalling/read-back verification. It omits a significant behavioral trait: dry_run defaults to true, so the default invocation is a preview rather than an actual reset.

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?

Front-loaded with the core action, then mechanism, precondition, and lifetime in short clauses. No filler sentences, though the parenthetical about addressable reset versus page-wide reset is slightly compressed and could be clearer.

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 description covers scope, mechanism, and reversibility. However, with five parameters, zero schema description coverage, and a dry_run default that changes the call's effect, the definition leaves material gaps an agent needs before invoking it correctly.

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 largely does not. Only the interaction-fingerprint requirement is implied, without explaining what a fingerprint is or how to obtain one; page_id, component_id, report_id and especially dry_run (default true, i.e., preview-only) are undocumented anywhere.

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: reset a rendered filter, parameter or date control to its saved default. It also scopes the mechanism ('addressable reset, not a page-wide reset or DOM keystrokes'), which distinguishes it from broader reset behavior. It stops short of naming a sibling like control_filter_set or control_parameter_set as the non-reset counterpart.

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?

Usage context is clear: use when a rendered control should return to its saved default, and the requirement of a current interaction fingerprint is stated as a precondition. It also points to operation_restore for undoing the reset. There is no explicit statement of when not to use it, e.g., to set a new value rather than revert.

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