Skip to main content
Glama

decker

by io.github.gigshow
OverviewDiscussionsAdmin

decker.get_assembly

THE answer for 'what is the situation and what do I do on this symbol now' — one verdict per symbol, built from the per-timeframe judgment state (CR1); no scores or weights. READ IN THIS ORDER: (1) verdict = state (direction · phase) + action: 진입 enter now (a new signal) | 유지 hold the existing stance, NOT a new entry | 청산 exit | 대기 wait; reason says why, until names the close that would change it. (2) summary_ko = ready-to-show Korean lines. (3) entry / stop / target / rr = the prices (entry.mode says whether it is a new entry or on hold — when the action is not 진입 it never says 'now'; target may be null with target.reason, e.g. no coordinate at least 2% from the entry price; rr mixes the entry timeframe's stop with the target timeframe's target). (4) as_of = the bar this answer is based on. Default = the answer only (about 3KB per symbol; summary_ko already narrates the next closes and the last signal). Pass detail=true for the structured detail: path (nearby prices and what a close there means), watch (upcoming bar closes in time order and the question each decides), story (this / last signal), ladders, matrix_summary (every timeframe's row incl. gate), tf_states (EVERY timeframe's own state: judgment stage, open reversal test with its confirm price, engine action, next-bar label chain, recently missed targets — none folded by direction), knots (every timeframe's decision prices ordered by distance from the price, up and down, with which timeframes and roles sit on each — the ORDER in which transactions would be reached, not a probability). reason may end with '반대 방향 반전 보류 중: …' = other timeframes whose reversal test runs AGAINST the verdict's direction, i.e. is testing the current stance (a fact, not a vote; it never changes the action). Omit symbol for all 14 symbols. Roles: frame = highest confirmed timeframe (sets direction and target); entry = lowest aligned timeframe whose signal is alive; 1w supplies direction/target only, never an entry. grade: 정렬 aligned | 되돌림 pullback against the frame | 전환 시험 frame under test | 재장전 no confirmed signal. Caveats: 정렬 does not mean every timeframe's gate is GO (check matrix_summary[].gate); entry.mode '지금' does not mean a new event this bar. Narrate or filter the result — do not re-decide coordinates.

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

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly: it explains that there are no scores or weights, what each action means, what reason/until convey, why target may be null, how rr mixes timeframes, approximate response sizes, and caveats such as 정렬 not implying every gate is GO. It also warns not to re-decide coordinates.

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 description is front-loaded with the core verdict purpose and then structured into a numbered reading order and a default-vs-detail explanation. It is dense and lengthy, but most content is relevant for a complex decision tool; the only weakness is that some caveats and interpretive notes make it heavier than necessary.

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 result shape and semantics; it does this in detail, covering verdict, summary_ko, entry/stop/target/rr, as_of, and the structured detail fields. For a complex multi-timeframe decision tool with two optional parameters, it is complete enough for correct invocation and interpretation.

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

Parameters5/5

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

Schema coverage is already 100%, but the description adds substantial meaning beyond the schema: detail=true is expanded into path/watch/story/ladders/matrix_summary/tf_states/knots, and omitting symbol is clarified as returning all 14 symbols. It also gives examples of symbol aliases and relative payload sizes.

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?

The description states a specific verb-and-resource purpose: 'one verdict per symbol' answering 'what is the situation and what do I do on this symbol now,' built from per-timeframe judgment state. It distinguishes the tool from raw-signal or market-state siblings by emphasizing a single verdict with action semantics and explicitly saying 'no scores or weights.'

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

Usage Guidelines4/5

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

It gives explicit usage instructions: read in a numbered order, default vs detail=true, omit symbol for all 14 symbols, and interpret action labels like 진입/유지/청산/대기. However, it does not explicitly name sibling tools or say when to use one of them instead, so the alternatives guidance is implicit rather than complete.

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

All decker toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources