Skip to main content
Glama

Count routes in a DAG

bpj_graph_acyclic_route_count
Read-onlyIdempotent

Count every directed route between two nodes of an acyclic graph as an exact integer string.

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

Input Schema

NameRequiredDescriptionDefault
endYes
graphYes
startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context — the result is an exact integer string (relevant because route counts overflow quickly) and the graph must be acyclic — but it never says what happens on a cyclic input or on unreachable 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?

One front-loaded sentence with no filler and no redundancy. It is efficient, though its terseness is partly the source of the missing detail rather than a virtue.

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?

For a simple three-parameter read-only tool with no output schema, the description covers the conceptual contract, but a tool whose main input is a free-form JSON adjacency string needs format guidance that is absent here. No output schema exists, so the 'exact integer string' note in the description is doing necessary work.

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%, so the three parameters carry only bare titles. The description does not explain the 'Directed adjacency map (JSON)' format, edge direction conventions, or whether start and end may coincide, 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?

States a specific verb (count), a specific resource (directed routes between two nodes), and a scope qualifier (acyclic graph). It is clearly distinguishable from traversal-style siblings such as minimum-hops or reachability tools, though it does not name any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrasing 'between two nodes of an acyclic graph,' so an agent can infer the general situation. There is no explicit when-to-use/when-not guidance versus neighboring graph tools, and no stated precondition or error behavior when the supplied graph is not acyclic.

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.