Skip to main content
Glama

Trace upstream impact

bpj_graph_upstream_impact
Read-onlyIdempotent

Find nodes that can reach a target, with their shortest upstream distances.

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>",
      "end": "<end>"
    },
    "name": "bpj_graph_upstream_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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. The description adds the useful behavioral fact that results are ranked or annotated by shortest upstream distance, but says nothing about output shape, behavior on cyclic graphs, or size limits implied by the 6000-character graph cap.

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 compact sentence with no filler, front-loading the traversal direction and the returned value. Nothing in it is redundant.

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

Completeness4/5

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

For a two-parameter, read-only computation tool with no output schema and clear annotations, the definition covers purpose and output content adequately. The remaining gap is the format expected for the adjacency map (key-to-neighbor-list shape), which matters because the schema provides no property descriptions.

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?

Schema description coverage is 0%, so the description carries the burden here. "Nodes that can reach a target" does clarify that traversal runs against edge direction and that 'end' is the destination, which is meaningful semantics for a directed adjacency input, but the JSON structure of the 'graph' parameter is never explained.

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: find nodes that can reach a target, plus the returned quantity (shortest upstream distances). That is clearly distinct from sibling graph tools like minimum_hops or reachability_index, but it never names an alternative to sharpen the boundary.

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 or when-not-to-use guidance and no mention of alternative tools for related traversal questions. The agent must infer from the sibling list alone whether it wants reverse reachability versus forward reachability or hop counts.

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.