den — Korean AEC knowledge, curated

Follow Order Relations (선후 관계 따라가기)

traverse

Read-onlyIdempotent

시공 순서와 선후 관계를 따라간다 — '무엇이 무엇보다 먼저 와야 하는가'. '기초부터 골조까지 순서', '거푸집 해체 전에 확인할 것' 같은 공정 질문에 쓴다. → 대신 쓸 것: 출발·도착 두 지점이 분명하면 path_between · 공정 전체 흐름을 한 번에 구성하려면 scenario · 두 공법 차이는 compare · 단순 수치·조문은 k_snippets. ★파라미터: relation=requires 는 선행 조건(이것보다 먼저 와야 하는 것), enables 는 후속 가능 작업, causes 는 인과, contrasts 는 대비다. 생략하면 전부 본다. direction=out 은 정방향(다음), in 은 역방향(이전) — 'X 전에 무엇을' 은 in 이다. depth 는 1~4 로 잘린다(넘겨도 4). limit 는 최대 스텝 수이고 depth 와 곱해 커진다. 빈 결과는 den 이 그 순서를 아직 갖고 있지 않다는 뜻이다 — 순서를 지어내지 않는다. 읽기 전용 · 외부 호출 없음.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`depth`	No	순회 홉 수 (1~4).
`limit`	No	최대 스텝 수.
`start`	Yes	시작 개념 이름/구문 (예: 거푸집).
`relation`	No	순회할 관계 (requires/enables/causes/contrasts 등). 생략 시 전체.
`direction`	No	out(정방향) 또는 in(역방향).	out

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses important behaviors: depth is truncated to 4, limit interacts with depth multiplicatively, and an empty result means the knowledge base does not yet contain that order — the tool does not invent ordering. This is significant added behavioral context.

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?

The description is dense but well-structured and front-loaded with the core purpose. Every section earns its place: usage examples, sibling routing, parameter semantics, depth/limit behavior, and empty-result interpretation. The compact formatting and symbols aid scanning without wasting words.

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?

For a graph-traversal tool with five parameters, the description covers purpose, alternatives, parameter meanings, edge-case behavior, and result interpretation. It also explicitly notes read-only behavior and no external calls, leaving no critical gap for an agent deciding whether and how to invoke it.

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?

Even though schema coverage is 100%, the description adds real semantic value by decoding each relation value: requires is a precondition, enables is a subsequent possible task, causes is causal, and contrasts is contrastive. It also explains direction with a concrete mapping: 'what before X' means direction=in.

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: it follows construction sequence and precedence relations, answering 'what must come before what'. It further distinguishes itself from siblings by naming path_between, scenario, compare, and k_snippets as alternatives for different question types.

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?

The description explicitly gives usage context with examples like 'order from foundation to frame' and 'what to check before formwork removal'. It also provides clear alternative routing: path_between when two endpoints are clear, scenario for a whole flow, compare for differences, and k_snippets for simple numbers or articles.

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

All den — Korean AEC knowledge, curated tools Inspect

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.