Skip to main content
Glama

Adjacency map to edge list

bpj_graph_edge_list
Read-onlyIdempotent

Export unique directed pairs and the full node list, including isolated nodes.

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

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=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond them by disclosing the shape of the result: deduplicated directed pairs plus a complete node list that retains isolated nodes. It does not disclose the output format (object vs. text), pagination, or failure behavior for malformed 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?

One sentence, front-loaded with the primary output and the isolated-node caveat trailing usefully. No filler, though the terseness leaves little room for the input-format detail an agent needs.

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 is responsible for conveying returns, and it does so in outline: pairs plus full node list. However, for a tool whose whole job is parsing a JSON adjacency map, the absence of any statement about input shape or output serialization leaves a real gap.

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?

The single parameter has 0% schema description coverage, so the description must carry the burden and it does not. Nothing is said about the expected adjacency map structure, key/value types, or the 6000-character maxLength constraint that will cause failures.

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 ('Export') and concrete outputs ('unique directed pairs and the full node list, including isolated nodes'), which distinguishes it from graph-analysis siblings such as bpj_graph_edge_density or bpj_graph_boundary_nodes. It does not name a sibling for comparison, so it falls short of a 5.

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 explicit when-to-use guidance, no prerequisites, and no named alternative among the many graph tools (density, bipartition, acyclic route count). The only scope hint is 'unique directed pairs', which implies deduplication but not usage context.

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.