Skip to main content
Glama

trace_cone

Trace the combinational fanin or fanout cone of a signal across hierarchy, stopping at flops, ports, and black boxes. Returns node counts and a frontier of boundary elements.

Instructions

Trace the combinational fanin/fanout cone of a term/net via naja's LogicCone. direction: fanin|fanout. The cone crosses hierarchy and combinatorial arcs and always stops at flops, top ports, and opaque black-box cells. Returns node_count, counts_by_kind, counts_by_model, and a frontier of {flops, ports, blackboxes} with exact counts and lists capped at max_frontier (<=200) with a truncation marker. cross_hierarchy groups the flop frontier by top-level submodule and, under outside_root_subtree, names the frontier registers that live OUTSIDE the cone root's own subtree (the cross-hierarchy answer) — read it directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
directionYes
max_frontierNo
Behavior5/5

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It details stopping conditions, return values (node_count, counts_by_kind, counts_by_model, frontier), frontier truncation at max_frontier, and cross_hierarchy grouping, providing comprehensive behavioral insight.

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 dense but each sentence adds value. It front-loads the purpose and logically describes behavior and return fields. Could be slightly more concise, but overall effective.

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?

The description covers tool behavior, parameters, and return values well. It explains the frontier structure and cross_hierarchy grouping. Lacks examples or exact formatting for counts, but for a specialized tool it is sufficiently complete.

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 0%, so the description must compensate. It adds meaning for direction (fanin|fanout) and max_frontier (<=200, caps lists), and implies path is a term/net. While not fully structured, it provides critical context beyond the bare schema.

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 clearly states the tool traces the combinational fanin/fanout cone of a term/net via naja's LogicCone, specifying direction and behavior (crosses hierarchy, stops at flops/ports/blackboxes). It distinguishes from siblings like get_drivers/get_loads by focusing on cones.

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?

The description implies usage for tracing combinational cones but does not explicitly state when to use this tool versus alternatives or provide conditions for use. No comparative guidance with sibling tools is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/najaeda/naja-scope'

If you have feedback or need assistance with the MCP directory API, please join our Discord server