Skip to main content
Glama

Directed node degrees

bpj_graph_degree_profile
Read-onlyIdempotent

Count inbound and outbound links and identify direct self-loops for each node.

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

Input Schema

NameRequiredDescriptionDefault
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world profile, so the safety story is covered. The description adds that self-loops are reported, which is useful behavior beyond annotations, but says nothing about result shape, edge-case handling (duplicate edges, dangling targets), or whether self-loops are also counted in the degree totals.

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

Conciseness5/5

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

A single front-loaded sentence with no filler. Every clause (inbound, outbound, self-loops, per node) carries distinct meaning.

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 one-parameter, read-only profile tool, the description covers what is computed but leaves the input format and output shape unspecified, and no output schema exists to fill that gap. Adequate but with clear omissions an agent would have to discover by trial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter, so the structural surface is minimal. However, the schema describes it only via a title, and the description offers no guidance on the adjacency-map JSON format or the 6000-character limit, which would matter for an agent constructing the input.

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 states a specific verb and resource: counting inbound and outbound links plus direct self-loops, per node. That cleanly separates it from sibling tools such as bpj_graph_edge_density or bpj_graph_reverse_links, though it never names an alternative explicitly.

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 prerequisites, and no mention of when a different graph tool (e.g. edge density or reverse links) would be a better fit. The only signal is the implicit 'for each node' scope, which an agent must infer.

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.