Skip to main content
Glama

Component Interaction State

component_interaction_state
Read-only

Read a component's current viewer selection, reset availability, and inherited cross-filters or slider filters in the browser session, without editing configuration or running queries.

Instructions

Read current native viewer selection, reset availability and inherited filters.

Returns onSelect behavior/default init separately from its runtime value, inherited cross-filters and slider filters. Effective filters are reported as unavailable (not_exposed_by_bundle), never as an empty-filter success. This is browser-session state, not a saved configuration edit or proof of query/data results. Rejects stale/dirty native models; report_refresh resets viewer state. No selection, reset, query refresh or report write is performed by this tool.

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

Input Schema

NameRequiredDescriptionDefault
page_idYes
report_idNo
component_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it discloses that effective filters are reported as unavailable (not_exposed_by_bundle) rather than an empty-filter success, that stale/dirty native models are rejected, that the state is browser-session scoped, and enumerates the mutations it does not perform. These are genuine agent-relevant behavioral traits not derivable from annotations.

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 layered caveats. Every sentence carries information, though the negative-enumeration sentence and the not_exposed_by_bundle aside make it denser than strictly necessary.

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 read-only state inspection tool with an output schema, the description covers scope, failure modes, and the freshness/validation contract well; return shape need not be explained. The remaining hole is parameter meaning, which neither schema nor description supplies.

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% across three parameters (page_id, report_id, component_id), so the description carries the burden of explaining them. It says nothing about any parameter — not what page_id/component_id scope the lookup to, nor why report_id is optional — leaving the agent to guess from field names alone.

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?

Opening sentence gives a specific verb and resource: 'Read current native viewer selection, reset availability and inherited filters.' The description also delineates scope against neighbouring concerns ('not a saved configuration edit or proof of query/data results', 'No selection, reset, query refresh or report write'), which lets an agent separate it from control_reset, report_refresh, and components_filters.

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 context is implied well: 'report_refresh resets viewer state' and the explicit negative list tell the agent this is not the tool for mutating or refreshing. However, there is no explicit when-to-use framing or a named alternative for reading saved configuration, so the routing is inferred rather than stated.

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