Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

set_timeframe

Change the open TradingView chart timeframe to a specified interval, then restore the prior setting afterward.

Instructions

Change the chart timeframe (1, 5, 15, 60, 240, D, W). Set it back afterwards.

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

Input Schema

NameRequiredDescriptionDefault
resolutionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the tool mutates shared chart state and should be reverted, but it says nothing about whether the change persists across sessions, affects other tools like screenshot or get_candles, fails on invalid resolutions, or requires a prior chart to exist.

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 short sentences, zero filler, with the core action and its allowed values front-loaded and the restore instruction trailing as a compact caveat. Nothing could be removed without losing information.

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 single-parameter tool with no output schema and no annotations, the definition covers the action, the valid domain, and the cleanup expectation. It could go further on persistence and side effects on sibling read tools, but it is adequate to call the tool correctly.

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% and the single parameter is a bare string, so the description must compensate and largely does by listing the legal resolution values (1, 5, 15, 60, 240, D, W). It does not state that the numeric values are minutes or clarify case sensitivity for D/W, leaving a small residual 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 and resource ("Change the chart timeframe") and enumerates the accepted resolutions, so an agent knows exactly what it mutates and what values it takes. It is clearly distinct from siblings such as set_visible_range, which concerns viewport range rather than timeframe.

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 phrase "Set it back afterwards" implies this is a temporary, transient change to be restored, which is useful usage context. However, there is no explicit guidance on when to prefer this tool, no note on prerequisites such as an active chart session, and no named alternative for related operations.

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