Skip to main content
Glama

Weakly connected groups

bpj_graph_weak_components
Read-onlyIdempotent

Find disconnected components while treating links as undirected.

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

Input Schema

NameRequiredDescriptionDefault
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 description contributes the non-obvious behavioral fact that edges are traversed as undirected regardless of the directed input format, but says nothing about result shape, ordering, or behavior on empty/malformed graphs.

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?

One sentence, front-loaded with the verb and result, with the crucial undirected caveat attached. Nothing is wasted, though the brevity leaves room that could have been spent on the input format.

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?

There is no output schema, so the description should at least sketch the return value (a list of component groupings?), and the input is a JSON adjacency map whose expected shape is never described. For a graph-analysis tool with an undocumented JSON parameter and no output contract, the definition is under-specified.

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% for the single required parameter, so the description must carry the burden — and it says nothing about the 'graph' argument. The only hints ('Directed adjacency map (JSON)', maxLength 6000) live in the schema's title, not the description, so the description adds no meaning beyond structured data.

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 states a specific verb ('Find') and resource ('disconnected components') and adds the decisive qualifier 'treating links as undirected', which is exactly what separates this from the weakly/strongly-connected sibling. It stops short of naming the contrasting tool, but the algorithmic distinction is unambiguous.

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 undirected qualifier implies when this tool applies versus a directed/strong-components variant, but no explicit alternative is named and no precondition is given (e.g. whether the graph must be a valid directed adjacency map first). Usage is inferable rather than stated.

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.