Skip to main content
Glama

Minimum-hop route

bpj_graph_minimum_hops
Read-onlyIdempotent

Find a shortest directed path between two nodes and count its hops.

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

Input Schema

NameRequiredDescriptionDefault
endYes
graphYes
startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 openWorldHint=false, so the safety profile is fully covered. The description adds that a path plus hop count is returned, but does not say what happens when no path exists or how hops are counted (edges vs. nodes).

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 no filler or redundant phrasing. It is efficient, though at this length the brevity shades into under-specification rather than pure economy.

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 three-parameter tool with no schema descriptions and no output schema, the definition leaves key facts unstated: the JSON shape of the adjacency map, whether an unreachable end yields an empty result or an error, and what unit 'hops' uses. These are things the agent needs in order to call and interpret the tool correctly.

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%: the three parameters carry only titles and length limits. The description mentions 'two nodes' generically but adds nothing about the required JSON adjacency format for 'graph' (maxLength 6000) or about start/end constraints, so it fails to compensate for the coverage gap.

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 a shortest directed path between two nodes and count hops. That is clearly distinct from sibling graph tools like bpj_graph_finite_diameter or bpj_graph_reachability_index, though no sibling is named for contrast.

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 guidance and no mention of alternatives such as a reachability or diameter tool. The only cue is the implied 'if you need a shortest path', which the agent must infer from the verb alone.

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.