Skip to main content
Glama

Topological waves

bpj_graph_topological_waves
Read-onlyIdempotent

Group a directed acyclic graph into successive zero-indegree waves.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "graph": "<graph>"
    },
    "name": "bpj_graph_topological_waves"
  }
}

Input Schema

NameRequiredDescriptionDefault
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The phrase 'successive zero-indegree waves' adds genuine algorithmic context, revealing iterative indegree peeling, but the description says nothing about cycle rejection, error behavior, or how waves are ordered within a level.

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?

A single front-loaded sentence with no filler, and the key concept (successive zero-indegree waves) is stated immediately. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should explain that the result is an ordered list of node sets, but it never says what is returned or in what form. For a computational graph tool taking a free-form JSON adjacency map, the missing return shape and cycle-handling notes are significant gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden, and it adds only the implicit constraint that the graph is directed and acyclic. The 'directed adjacency map (JSON)' format, the node-id-to-neighbor-list convention, and the 6000-character limit are left entirely to the schema title.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: grouping a directed acyclic graph into successive zero-indegree waves, which precisely names the topological-layering computation. It does not, however, distinguish itself from graph siblings such as bpj_graph_acyclic_route_count or bpj_graph_minimum_hops, which also operate on directed graphs.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over the many other graph tools, and no stated preconditions beyond the implicit 'acyclic' requirement. An agent cannot tell from the text what to do when the input contains a cycle or when wave layering is preferable to plain reachability or degree analysis.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.