Skip to main content
Glama

set_focus

Set the active board focus to item or frame IDs, including frame children, or clear it with an empty list so work starts from the user's current context.

Instructions

Set the focus to these ids (frames include their children), or [] to clear. Focus is the part of the board the user is working on now: start from it and prefer it, but it is not a boundary; read or reference other items when the task needs them (old ideas, related frames).

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

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations establish this is a non-read-only, non-destructive, non-open-world mutation, so the safety profile is already covered. The description contributes beyond that by explaining hierarchical inheritance (frames include children) and the clearing idiom, both non-obvious side effects of the call.

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?

The action and its edge cases are front-loaded in the first sentence, with the interpretive guidance following. The second sentence is long and could be trimmed, but every clause conveys a distinct instruction about how to treat focus.

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 simple one-parameter mutation with no output schema, the description covers what the tool does, its inheritance and reset behavior, and how focus should influence subsequent work. It omits failure behavior for unknown ids, which is a minor gap given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'ids' array, so the description must carry the meaning, and it does: it explains that the array holds target ids, that frames imply their children, and that [] is the reset value. It doesn't specify which id types are accepted (items vs frames) or ordering behavior, leaving a small gap.

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 names a specific verb and resource ("Set the focus to these ids") and adds two concrete behaviors an agent could not guess: frames bring their children, and an empty array clears focus. It doesn't explicitly contrast with the sibling get_focus, but the set/clear semantics are unambiguous enough to distinguish them in practice.

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?

The second sentence tells the agent how to treat focus once set (start from it, prefer it, but still read other items when needed), which is useful downstream behavior. It never says when an agent should call set_focus versus leaving focus alone, so actual invocation guidance is only implied.

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