Skip to main content
Glama

set_current_timeline

Sets the specified timeline as the active open timeline so subsequent Resolve operations target the correct timeline.

Instructions

Make a timeline the current (open) one.

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

Input Schema

NameRequiredDescriptionDefault
timelineYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows it is a non-destructive state change. Beyond that, the description adds nothing: it does not say whether the switch is persisted, what happens to the previously current timeline, or whether it fails when the timeline does not exist. The sentence largely restates the tool name.

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, front-loaded, with no filler. It is efficient, though the terseness borders on under-specification rather than over-verbosity.

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 one-parameter, non-destructive setter with no output schema, a single sentence covers the essentials of what changes. The missing piece is the identifier semantics of the string-or-integer argument, which the annotations cannot supply.

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% for the single required 'timeline' parameter, and the description offers no help. Critically, the schema accepts either a string or an integer, and the description never clarifies whether that means a name, an index, or an id, which is exactly the ambiguity that would cause a failed call.

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 gives a concrete verb ('Make') and resource ('a timeline') plus the resulting state ('current (open) one'), which is enough to separate it from siblings like create_timeline or append_to_timeline. It stops short of explaining what 'current' means operationally, but the core purpose is unambiguous.

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 statement of when to use this versus alternatives such as get_timeline or set_current_bin, and no prerequisite context (e.g. that a project must be open). The only guidance is the parenthetical '(open)', which implies but does not state the effect.

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