Skip to main content
Glama

decker.get_view

Ready-to-show Korean status card for a symbol — the same card the daily briefing sends, built from the same consumer contract (CR1) as decker.get_market_state, so direction and prices always agree with it. Shows the timeframes grouped 상위/중간/단기 with one line each (direction + stage + the price that decided it), the nearby prices to watch, and a short explanation of the chosen timeframe (tf, default 4h): what closed beyond what, whether the signal flips the previous one, entry/target/stop. Also returns direction (+/- only while that timeframe's signal is pending or confirmed; a failed or absent signal gives no direction — failure does not assert the opposite side), wait_target, invalidation, ref_price and recent self-scoring verdicts. Use this when you want text to show as-is; use decker.get_market_state when you want structured values to reason over. layer=STATE_VIEW: a market-state reading, NOT a trade instruction. The response carries TWO readings: the timeframe card (lines, top-level direction/phase — that one timeframe's own state, its action words are about that timeframe) and verdict (the symbol's single judgment across timeframes — the one to act on). They can differ (e.g. card direction null / '매도 유지' while verdict is '진입'); direction_basis says which is which and direction_basis.differs flags it. Before placing any order through any execution tool, check the intent with decker.validate_intent.

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": {
      "symbol": "<symbol>"
    },
    "name": "decker.get_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
tfNoOptional view timeframe — the grounded narrative is composed on this TF's bar (e.g. '1h' when the user asks about the 1-hour picture). Omit for the engine's default action TF (usually 4h, same as the daily briefing card).
symbolYese.g. BTCUSDT, XYZ_GOLDUSD (crypto + HL TradFi synthetics; KRX daily lineage not yet covered by view v1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: it declares layer=STATE_VIEW (not a trade instruction), explains the two readings (timeframe card vs verdict) and that they can differ, defines when direction is populated, and warns that a failed/absent signal does not assert the opposite side. It also enumerates returned fields such as wait_target, invalidation, ref_price, direction_basis.differs, and self-scoring verdicts.

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 purpose and the key sibling distinction are front-loaded in the first two sentences, followed by output structure and then the critical two-readings warning. It is dense and long, but the length is justified by the complexity of the return contract; a small amount of repetition around direction semantics could be trimmed.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must explain the return shape and it does: card lines grouped 상위/중간/단기, nearby prices, timeframe explanation, direction/phase, verdict, wait_target, invalidation, ref_price, and scoring verdicts. It also covers the ambiguity an agent most needs to resolve, namely card direction vs verdict and how direction_basis distinguishes them.

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 the schema already explains symbol and tf, including the default action TF. The description adds only marginal meaning by restating the tf choice context ('chosen timeframe') and reinforcing the 4h default. Baseline 3 is appropriate because the schema does the heavy lifting.

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+resource: builds a ready-to-show Korean status card for a symbol, and explicitly ties it to the same consumer contract as decker.get_market_state so output agrees. It names the sibling it differs from, so an agent can separate the text-rendering view from the structured-value tool without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule: 'Use this when you want text to show as-is; use decker.get_market_state when you want structured values to reason over.' It also adds a required pre-order step: check intent with decker.validate_intent before executing. Alternatives and a hard prerequisite are both stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.