Skip to main content
Glama
Sign In

Warmth Engine Observatory

by com.warmthengine
OverviewDiscussionsAdmin

Traverse Coordination Lineage

traverse_coordination
Read-onlyIdempotent

Walk the Coordination Topology lineage graph (precomputed lookups over the parent→child Coordination Connection DAG). mode="path" returns every path between source and target, each with its CC-type (connection-type) sequence and whether it is pure lineage (homogeneous) or crosses a sibling/bidirectional edge; mode="ancestors"/"descendants" return the nodes reachable up/down the hierarchy; mode="neighbours" returns direct parents and children. For a node's structural metrics or the whole-graph summary rather than walks, use get_topology. cc_types (connection-type filter) and max_depth apply to path AND to the ancestors/descendants/neighbours adjacency walks — supplying either runs a bounded typed walk over the backbone edges. homogeneous_only is path-only (drops any path crossing a sibling edge); sent to an adjacency mode it is returned in ignored_params. A bare numeric node_id missing the E prefix is resolved (the canonical form is echoed as resolved_node_id); a node that exists but carries no backbone edges is reported as such rather than as unknown.

Input Schema

NameRequiredDescriptionDefault
modeYesTraversal mode
sourceNoSource node id for mode=path
targetNoTarget node id for mode=path
node_idNoNode id for ancestors | descendants | neighbours (e.g. "E93"; a bare "93" is resolved)
cc_typesNoEdge-type (connection-type) filter, applied to path and adjacency walks; default = all types
max_depthNoMaximum walk depth — path length in mode=path, hop count from node_id in the adjacency modes
homogeneous_onlyNomode=path only — true → drop any path crossing a sibling (Type 6/7) edge; ignored (and echoed in ignored_params) on adjacency modes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cc_types / items / enum
      Added value: +[
+  1,
+  2,
+  3,
+  4,
+  5,
+  6,
+  7
+]
    • removedInput schema / properties / cc_types / items / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / cc_types / items / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / cc_types / items / type
      Previous value: -"integer"New value: +"number"
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed4 schema fields changed
    • changedInput schema / properties / cc_types / description
      Previous value: -"Edge-type (colour) filter; default = all 7"New value: +"Edge-type (connection-type) filter, applied to path and adjacency walks; default = all types"
    • changedInput schema / properties / homogeneous_only / description
      Previous value: -"true → drop any path crossing a sibling (Type 6/7) edge"New value: +"mode=path only — true → drop any path crossing a sibling (Type 6/7) edge; ignored (and echoed in ignored_params) on adjacency modes"
    • changedInput schema / properties / max_depth / description
      Previous value: -"Maximum path length"New value: +"Maximum walk depth — path length in mode=path, hop count from node_id in the adjacency modes"
    • changedInput schema / properties / node_id / description
      Previous value: -"Node id for ancestors | descendants | neighbours"New value: +"Node id for ancestors | descendants | neighbours (e.g. \"E93\"; a bare \"93\" is resolved)"
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: it discloses the ignored_params echo when homogeneous_only is sent to an adjacency mode, the resolved_node_id echo for bare numeric ids, and that a node with no backbone edges is reported distinctly rather than as unknown. It does not discuss result size or any caps on the number of paths returned.

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?

Purpose and mode semantics are front-loaded, then parameter interactions, then id-resolution behavior. Dense but every clause carries information (mode contracts, scope of filters, ignored-param behavior); no filler sentences.

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?

There is no output schema, but the description compensates by describing what each mode returns (paths with CC-type sequences and pure-lineage flag, reachable nodes, direct parents/children) plus the echoed fields. For a 7-parameter graph-walk tool this is close to complete; only result-size limits or empty-result semantics are unaddressed.

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 100%, so the baseline is 3, but the description adds cross-parameter semantics the schema cannot express: cc_types and max_depth apply to path AND adjacency walks, homogeneous_only is path-only and is echoed in ignored_params otherwise, and a bare node_id is resolved to the canonical E-prefixed form. That is meaningful meaning beyond the per-field descriptions.

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 (walk) and resource (Coordination Topology lineage graph) and enumerates the four modes with what each returns. It also explicitly separates itself from the sibling get_topology ('For a node's structural metrics or the whole-graph summary rather than walks, use get_topology'), so an agent can route between the two without opening a 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?

Names the alternative tool and the exact condition that selects it, and explains which mode to pick for each intent (path vs ancestors/descendants vs neighbours). Nothing about when to use this versus get_topology is left to inference.

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

All Warmth Engine Observatory toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources