Skip to main content
Glama

decker.get_assembly

THE answer for 'what is the situation and what do I do on this symbol now' — one verdict per symbol from the per-timeframe judgment state (CR1); no scores or weights. TWO LAYERS — TOP = the machine's judgment, BOTTOM = its sources. READ THE TOP FIRST: top_ko (also the first lines of summary_ko) = 4 judged lines: ① 지금 시장 — the theme (the latest still-current close transition — a target touch or an outcome — of the 1w/1d judgment loops, else 4h/1h/30m; several target→judgment loops run at once in each timeframe), lower-timeframe outcomes in that period (진행 progress | 테마 반대 against it), tests against the theme (막히는 중 blocked | 넘는 중 crossing) → the conclusion ② 행동 action + one reason ③ 목표 next cells in the theme direction · 무효화 the confirm price of the highest test against the theme ④ 다음 결정 the next closes in time order with what each outcome means, and which side the current price is on now. BOTTOM (sources): verdict = state + action (진입 enter now, a new signal | 유지 hold, NOT a new entry | 청산 exit | 대기 wait), reason and condition (the nearest closes that would change it); entry / stop / target / rr (entry.mode says new entry or hold; target may be null with target.reason); as_of = the bar it is based on. With symbol also readings/events (get_market_state lines). detail=true adds path, watch, story, ladders, matrix_summary (every timeframe incl. gate), tf_states, knots. grade = the theme's phase (test | confirm | null). head_horizons_ko = per-horizon lines (a GO timeframe below the theme is a piece for that horizon, not the symbol answer; 1w is a horizon only). Omit symbol for all 14 symbols. Narrate or filter the result — do not re-decide coordinates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "decker.get_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoInclude path / watch / story / ladders / matrix_summary (about 20KB per symbol). Default false: the answer only.
symbolNoOptional symbol or alias (BTC, 비트코인, GOLD, 테슬라...). Omit for all 14 symbols.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / detail / description
      Previous value: -"Include path / watch / story / ladders / matrix_summary. Default: true with a symbol, false without."New value: +"Include path / watch / story / ladders / matrix_summary (about 20KB per symbol). Default false: the answer only."
    • changedInput schema / properties / symbol / description
      Previous value: -"Optional symbol or alias (BTC, 비트코인, GOLD, 테슬라...). Omit for all 14 symbols (answer only)."New value: +"Optional symbol or alias (BTC, 비트코인, GOLD, 테슬라...). Omit for all 14 symbols."
  2. Changed2 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Include path / watch / story / ladders / matrix_summary. Default: true with a symbol, false without.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / symbol / description
      Previous value: -"Optional symbol or alias (BTC, 비트코인, GOLD, 테슬라...). Omit for the full universe."New value: +"Optional symbol or alias (BTC, 비트코인, GOLD, 테슬라...). Omit for all 14 symbols (answer only)."
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it discloses a lot about output shape and cost (detail adds ~20KB per symbol, target may be null with target.reason, entry.mode semantics) and gives a behavioral constraint ('Narrate or filter the result — do not re-decide coordinates'). It never states that this is a read-only, side-effect-free operation, nor anything about auth or rate limits, which is the main gap for a zero-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly — the first sentence is the verdict statement — and most sentences carry information with no filler. But it is very long for a two-parameter tool, packs enumerated output structure into prose, and mixes Korean labels with English inside dense clauses, making it costly to parse rather than scannable.

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?

With no output schema, the description must explain returns, and it does so thoroughly (top/bottom layers, verdict/action states, reason/condition, entry/stop/target/rr, as_of, grade, head_horizons_ko, detail extras). Combined with a 100%-covered two-param schema, an agent has enough to call it correctly; only the safety/read-only profile and explicit sibling exclusion are missing.

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 coverage is 100% and both parameters are described there, so the baseline is 3. The description largely repeats the schema (detail ~20KB per symbol, omit symbol for all 14) and adds only marginal meaning — the substantive content is about return payloads, not the two inputs.

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?

Opens with a specific, concrete claim: 'one verdict per symbol from the per-timeframe judgment state (CR1); no scores or weights', which tells an agent exactly what resource this returns and what it is not (no scores/weights). It is distinguishable from get_market_state (raw lines, referenced only as the source of readings/events) and from get_signals. However, the core statement is buried in dense internal jargon ('CR1', 'top_ko', 'knots', 'ladders') that an uninitiated agent must reverse-engineer.

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?

It implies the use case strongly ('THE answer for what is the situation and what do I do on this symbol now') and gives ordering advice ('READ THE TOP FIRST') plus a scope rule ('Omit `symbol` for all 14 symbols'). But it never explicitly routes against siblings — there is no statement like 'use get_market_state for raw lines, use get_view for X'. Sibling differentiation must be inferred from the parenthetical mention of get_market_state lines.

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.