Skip to main content
Glama

Identify graph boundaries

bpj_graph_boundary_nodes
Read-onlyIdempotent

Separate sources, sinks and isolated nodes in a directed graph.

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

Input Schema

NameRequiredDescriptionDefault
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds nothing beyond that: it does not say how isolation is defined (no edges at all vs. no in/out neighbors), how the three groups are returned, or how malformed input is handled.

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?

It is a single front-loaded sentence with no wasted words, which is good, but its brevity comes at the cost of under-specification rather than achieved economy. There is no structure to the sentence beyond a flat clause.

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 explain what the return value looks like (three collections? a mapping?), and with a 0%-documented input parameter it should also sketch the input format. Neither is present, leaving the agent unable to call the tool confidently.

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; the schema only says 'Directed adjacency map (JSON)' with a 6000-char limit. The description does not supply the expected shape (e.g. {"A":["B","C"]}), whether keys or values may be empty, or whether node identity comes from keys or values — so the coverage gap is not compensated.

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

Purpose3/5

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

The description names a concrete resource (a directed graph) and the categories being produced (sources, sinks, isolated nodes), which is more specific than the title. But the verb 'Separate' is ambiguous — it could mean split, classify, or return three lists — and nothing distinguishes this from other graph-structure siblings like degree_profile or weak_components.

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 use this tool, no prerequisites, and no mention of adjacent tools that also analyze node degree or connectivity. An agent must infer the use case entirely from the phrase 'sources, sinks and isolated nodes'.

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.