Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

Rig Edge

rig_edge

Wire or unwire ONE edge between two EXISTING blocks of a canvas rig — 'connect the fetch step to the judge', 'route the critique back to revise when it says REVISE', 'disconnect A from B'. Identify both ends by node id, label, skill name, or 1-based position. Add guard ({source, op, value?}) to make the edge a CONDITIONAL route — how a loop gets its exit condition on a stateful_graph. remove: true drops the from→to edge instead. Re-wiring an edge that already exists UPDATES its kind/guard in place. Returns the fresh block-by-block summary incl. the full edge topology; the Builder canvas updates live. (rig_node_add's after wires only at creation — this is the tool for every rewiring after that.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesDestination block: same identifiers
fromYesSource block: node id, label, skill name, or 1-based position
kindNo'data' (default) | 'control' | 'conditional' (implied when guard is set)
guardNoTake this edge ONLY when the condition holds — {source, op, value?}. `source` is a `{{node.port}}` channel ref; `op` = eq | not_eq | contains | gt | gte | lt | lte | truthy | exists.
removeNotrue = drop the from→to edge instead of adding one
rig_idYesUUID of the rig (rig_search finds it)
wallet_addressYesOwner scope

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / guard / description
      Previous value: -"Take this edge ONLY when the condition holds — {source, op, value?}. `source` is a `{{node.port}}` channel ref; `op` = eq | not_eq | contains | gt | lt | truthy | exists."New value: +"Take this edge ONLY when the condition holds — {source, op, value?}. `source` is a `{{node.port}}` channel ref; `op` = eq | not_eq | contains | gt | gte | lt | lte | truthy | exists."
    • changedInput schema / properties / guard / properties / op / enum
      Previous value: -[
-  "eq",
-  "not_eq",
-  "contains",
-  "gt",
-  "lt",
-  "truthy",
-  "exists"
-]New value: +[
+  "eq",
+  "not_eq",
+  "contains",
+  "gt",
+  "gte",
+  "lt",
+  "lte",
+  "truthy",
+  "exists"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Adds real context beyond annotations: re-wiring an existing edge UPDATES kind/guard in place, `remove: true` drops the edge, the canvas updates live, and the return is a block-by-block summary with full topology. Annotations (readOnlyHint=false, destructiveHint=false) cover the safety profile; the description adds mutation semantics. Minor gap: no explicit permission/auth note.

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?

Dense but front-loaded: the core verb and the sibling disambiguation lead, with guard/remove details following. Slightly packed into one long paragraph, but every sentence carries operational information.

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?

Despite no output schema, the description states what is returned (fresh block-by-block summary incl. edge topology) and the live canvas side effect. With 7 params at 100% coverage and annotations present, nothing an agent needs to invoke correctly is missing.

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 goes further: it explains guard as the mechanism for a conditional route and a loop's exit condition, and enumerates the four ways to identify an endpoint. That adds meaning beyond the schema's own 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 pair (wire/unwire) and resource (ONE edge between EXISTING blocks) with concrete natural-language examples of the operation. Explicitly distinguishes itself from rig_node_add's `after` parameter, so an agent can choose correctly without opening schemas.

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 (rig_node_add's `after` wires only at creation) and states when this tool is required ('every rewiring after that'). Also gives the guard-vs-remove decision conditions and the identity options for endpoints.

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

All Rokha toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources