Skip to main content
Glama

Reduce transitive links

bpj_graph_transitive_reduction
Read-onlyIdempotent

Remove edges with alternate routes while preserving reachability in a directed acyclic graph.

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

Input Schema

NameRequiredDescriptionDefault
graphYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is covered. However, the phrase 'Remove edges' is ambiguous against those annotations: it is not clarified whether the tool mutates the supplied graph or returns a new reduced edge set, which is exactly the kind of behavioral detail the description should add on top of the annotations.

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; the core operation and its invariant are stated immediately. It is arguably under-specified rather than verbose, so the terseness costs nothing structurally but leaves gaps elsewhere.

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?

There is no output schema, so the description should state what is returned (a reduced edge set, a list of removed edges, or a full graph object) and it does not. For a one-parameter, annotation-covered, mathematically well-defined operation this is adequate but incomplete.

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% and there is a single required parameter, yet the description adds almost no meaning about it beyond the DAG constraint. It does not explain the expected JSON adjacency-map format, how isolated nodes or self-loops are handled, or the 6000-character limit, leaving the agent to infer the input shape from the schema title alone.

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 specific operation on a specific resource: removing edges that have alternate routes while preserving reachability, i.e. transitive reduction. It is unambiguous about what is computed, though it never uses the term 'transitive reduction' (only the title does) and does not distinguish itself from graph-analysis siblings such as reachability or edge-list tools.

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?

The only usage signal is the precondition 'in a directed acyclic graph', which usefully tells the agent the input must be a DAG. There is no guidance on when to prefer this over related siblings (reachability index, edge list, cycle witness) and no statement of what happens if the input contains cycles.

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.