Skip to main content
Glama

Directed reachable diameter

bpj_graph_finite_diameter
Read-onlyIdempotent

Find the longest shortest distance over reachable directed pairs.

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

Input Schema

NameRequiredDescriptionDefault
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/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 fully covered elsewhere. The description's only added behavioral content is the 'reachable directed pairs' qualifier, which usefully signals that unreachable pairs do not inflate the result. It says nothing about empty-graph handling, output type, or computational cost on large adjacency maps.

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 short sentence with no filler, and the core computation is front-loaded. It is terse rather than padded, though the terseness borders on under-specification for an agent unfamiliar with graph jargon.

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

Completeness3/5

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

With no output schema, the description should indicate the return value (integer diameter, and what happens for an empty or disconnected graph), which it does not. The input format is likewise undocumented. For a one-parameter pure-computation tool this is workable but leaves real ambiguity.

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?

There is a single parameter, and schema description coverage is 0% — the schema offers only the title 'Directed adjacency map (JSON)' and a 6000-character cap. The description does not show or describe the expected JSON shape (e.g. node-to-neighbor-array mapping), leaving the agent to guess the serialization format for a required input. This is a substantive gap the description should have closed.

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 names a precise computation: the maximum over reachable directed pairs of the shortest path length, i.e. the directed diameter. That is a specific verb-plus-resource statement an informed agent can map to a single operation. It does not, however, distinguish itself from graph siblings such as bpj_graph_minimum_hops or bpj_graph_reachability_index, which could plausibly return overlapping information.

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 choose this tool over the many other graph tools, and no stated preconditions. The phrase 'over reachable directed pairs' hints that unreachable pairs are excluded, but the agent is left to infer whether a disconnected graph returns a finite value, null, or an error.

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.