Skip to main content
Glama

Strongly connected groups

bpj_graph_strong_components
Read-onlyIdempotent

Partition nodes by mutual reachability along directed edges.

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_strong_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. Beyond that the description says nothing about what is returned (grouping shape, node ordering, how singletons or disconnected nodes are treated) and no output schema exists to compensate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no filler and the core condition front-loaded, which is structurally sound. Its brevity is achieved by omission rather than by efficient phrasing, so it is concise but under-specified.

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?

For a single-parameter tool with no output schema and zero schema description coverage, the description should carry the input format and return shape. It supplies neither, leaving an agent unable to construct or interpret a call without guessing.

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% and the single parameter carries only a bare title, "Directed adjacency map (JSON)", with a maxLength cap. The description hints at "directed edges" but does not explain the expected JSON shape, key/value meaning, or the 6000-character limit, so the format gap is left unbridged.

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?

"Partition nodes by mutual reachability along directed edges" states a specific operation and the defining condition of strong connectivity, which implicitly separates it from weak components. It stops short of naming the sibling alternative, so the agent must infer the strong-vs-weak distinction.

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 when-to-use guidance, no mention of when a weak-component or reachability tool would be preferable, and no prerequisites or input constraints. The agent gets a definition of the algorithm but no routing signal.

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.