Skip to main content
Glama
the-real-talk

the-real-talk

set_explicit_variable_mode

Pin a variable collection's mode to a node and all its children by ID or name, or clear the pinned mode to restore inherited behavior.

Instructions

Pin the mode of a variable collection on a node and all its children (for example a column in a given mode). Node, collection and mode can be given by ID or by name. Set clear to true to remove the pinned mode.

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": {
      "node": "<node>",
      "collection": "<collection>"
    },
    "name": "set_explicit_variable_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoID or name of the mode (required unless clear is true)
nodeYesID or name of the node (a name must be unique on the current page)
clearNotrue to remove the pinned mode of this collection on the node
collectionYesID or name of the variable collection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations to carry the burden, the description does disclose the most important non-obvious trait: the pin cascades to all children of the node. It also explains the clear flag's destructive effect of removing the pinned mode, and that identifiers may be IDs or names. It stops short of error behavior (unknown mode, non-unique name) or permission requirements.

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?

Two sentences, front-loaded with the action and its scope, followed by identifier flexibility and the clear-flag behavior. The column example is short and genuinely clarifies the use case, so nothing is wasted.

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 four-parameter mutation tool with no annotations and no output schema, the description covers the cascade effect, the removal path, and the identifier modes needed to call it correctly. What remains missing is failure behavior and any indication of what the tool returns, which is a modest gap rather than a blocker.

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 100%, so every parameter is already documented, including the 'required unless clear is true' condition for mode. The description reinforces the ID-or-name flexibility across all three lookup parameters but adds no syntax, format, or resolution-order detail beyond the schema.

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?

The description uses a specific verb and resource: 'Pin the mode of a variable collection on a node and all its children', with a concrete illustration of pinning a column to a mode. It implicitly separates itself from mode-management siblings such as add_variable_mode by targeting a node rather than a collection, but it never names those siblings explicitly.

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?

It states a usage-style behavior for the removal path ('Set clear to true to remove the pinned mode'), which tells the agent this tool both sets and clears. However, there is no guidance on when to prefer this over add_variable_mode or set_variable_value, and no prerequisites or caveats are given.

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