Skip to main content
Glama

jump_to_tab_by_name

Activate a Blender workspace by its name to switch tabs directly, avoiding manual navigation in the UI.

Instructions

Activate the workspace with the given name.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already establish this is non-read-only, non-destructive, and confined to the local session. The description adds nothing beyond that: it does not say what 'activate' entails for the current viewport/editor state, whether the current selection or unsaved view is disturbed, or how a missing name is reported. For a state-changing tool this is thin.

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?

One short sentence, action front-loaded, no filler. It is efficient, though the brevity is partly the source of the documentation gaps rather than a virtue of tight writing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 explained here. Even so, a navigation tool with an undocumented string identifier and no fallback behavior described leaves the agent guessing on matching semantics and failure modes, which are the two things it actually needs.

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 carries the full burden for the single 'name' parameter. 'With the given name' only restates the schema key; it does not say whether the name is an exact string, case-sensitive, a tab label versus a workspace/file name, or what a near-miss does. The coverage gap is essentially uncompensated.

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: 'Activate the workspace'. An agent can tell this is a navigate/focus action targeting a named workspace. It loses a point because the tool name says 'tab' while the description says 'workspace', and because it draws no line between itself and the sibling jump_to_tab_by_space_type.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the by-space-type sibling, no stated prerequisite (e.g. the workspace must already be open), and no note on what happens if the name does not exist. Usage must be inferred entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.