Skip to main content
Glama

Reachability index

bpj_graph_reachability_index
Read-onlyIdempotent

List the other nodes each node reaches over one or more directed links.

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

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 the safety profile is fully covered. The description adds the one behavioral nuance annotations cannot carry: reachability is transitive ("over one or more directed links"), not single-hop. It says nothing about cycle handling, self-reachability, or the cost/size ceiling imposed by the 6000-character input limit.

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?

A single front-loaded sentence with zero padding. It is efficient, though the extreme brevity pushes some necessary detail into the gaps rather than into the sentence.

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 must carry the return-value burden, and it does not: it never states that the result is a node-to-reachable-nodes mapping, whether unreachable nodes still appear as empty entries, or whether a node in a cycle lists itself. For an algorithm tool returning a computed structure, these omissions are material.

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

Parameters3/5

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

With a single parameter at 0% schema description coverage, the schema offers only a title, "Directed adjacency map (JSON)," and a maxLength. The description confirms the input is a directed graph and that reachability follows directional links, but gives no concrete encoding example, no rule for nodes with no outgoing edges, and no guidance on what happens at the 6000-character cap.

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 ("List") and a specific computed resource (the nodes each node reaches over one or more directed links), which pins down transitive forward reachability rather than direct edges. It is distinguishable from most siblings, though an agent could still hesitate between this and bpj_graph_upstream_impact or bpj_graph_transitive_reduction since neither is named or excluded.

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 prerequisites, and no mention of any alternative tool. The only implicit cue is "one or more directed links," which hints at transitive closure versus a direct-edge listing, but the agent must infer that on its own.

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.