Skip to main content
Glama

Directed edge density

bpj_graph_edge_density
Read-onlyIdempotent

Compare distinct nonloop edges with the number of possible ordered 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_edge_density"
  }
}

Input Schema

NameRequiredDescriptionDefault
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say the result is a normalized ratio in [0,1], how degenerate inputs (empty graph, single node, zero possible pairs) are handled, or what the response shape is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, which is good for front-loading, but the terseness crosses into under-specification rather than efficiency. It reads like a formula fragment rather than an instruction.

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 computation tool with no output schema and an undocumented input format, the description should state the result type and edge-case behavior. Neither is present, so an agent cannot confidently construct the graph payload or interpret the returned value.

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?

With one required parameter at 0% schema description coverage, the description must carry the burden of explaining the 'graph' argument. It does not mention that the input is a JSON adjacency map, what the key/value structure looks like, or the 6000-character limit, so the schema title is the only clue an agent gets.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence names the specific quantity being computed (distinct nonloop edges versus possible ordered pairs), which effectively defines directed edge density without using the term. However, it is phrased as 'Compare X with Y' rather than stating a verb like 'compute the ratio', and it gives no signal distinguishing it from siblings such as bpj_graph_edge_list or bpj_units_density.

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 guidance, no mention of when a directed density measure is preferable to alternatives in the graph family, and no prerequisites or exclusions. The agent must infer applicability entirely from the tool name.

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.