Skip to main content
Glama

Control Date Range Set

control_date_range_set

Set an absolute YYYYMMDD date range on a report date-range control using its native select behavior, with preview, conflict checks, read-back and reversal; saved defaults stay unchanged.

Instructions

Set an absolute YYYYMMDD runtime range on a date-range control.

Uses the component's native onSelect behavior. Browser-session-only, previewed, conflict-guarded, journalled, read back and reversible in the same document. Saved defaults are unchanged; control_reset returns to the saved default.

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_date_range_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.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the write is session-scoped, previewed (consistent with dry_run defaulting true), conflict-guarded, journalled, read back after application, and reversible within the same document. This tells the agent mutation safety, reversibility, and persistence boundary — none of which the readOnlyHint/destructiveHint flags convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core action and value format, then behavioral guarantees, then the persistence boundary and alternative. No filler or restatement of the title.

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?

An output schema exists, so return-value explanation is unnecessary, and the description thoroughly covers mutation semantics, reversibility, and scope for a 6-parameter nested-object write tool. The remaining gap is the undocumented identity/fingerprint parameters, which an agent must infer from the schema alone.

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?

With 0% schema description coverage, the description must carry parameter meaning; it clarifies the nested value object as absolute YYYYMMDD start/end anchors and hints at expected_interaction_fingerprint via 'conflict-guarded' and dry_run via 'previewed'. However, page_id, component_id, and report_id remain unexplained, so it only partially compensates for the coverage gap.

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?

States a specific verb ('Set') and resource ('a date-range control') plus the value shape ('absolute YYYYMMDD runtime range'), which is precise enough to distinguish it from sibling setters like control_filter_set or control_parameter_set. It also names control_reset as the contrasting operation.

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?

Explicitly frames the tool as a runtime-only change ('Browser-session-only... Saved defaults are unchanged') and names the alternative, control_reset, for returning to the saved default. It does not spell out when to prefer this over other control setters, but the runtime-vs-persisted distinction covers the main decision.

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