Skip to main content
Glama

Find articulation vertices

bpj_graph_cut_vertices
Read-onlyIdempotent

Ignore direction and find vertices whose removal increases the component count.

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

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 establish readOnly, idempotent, non-destructive and closed-world behavior, so the description's remaining job is semantic. It does add the important trait that edge direction is disregarded, which the schema's 'Directed adjacency map' title would otherwise leave ambiguous. It says nothing about what is returned (vertex list format, ordering, behavior on disconnected or empty graphs).

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?

One tight sentence with the key interpretive caveat ('ignore direction') front-loaded before the operation. No filler, no restating the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, annotation-covered, output-schema-free analysis tool, this is close to sufficient: the operation and the direction-agnostic behavior are stated. The remaining gap is that the agent learns nothing about the accepted input encoding or the shape of the returned vertex collection.

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% for the single required parameter, so the description must carry the load and does not: the JSON adjacency-map encoding, key/value format, and the 6000-character limit are documented only by the schema's bare title and maxLength. 'Ignore direction' is the only hint about how input is interpreted, and it is indirect.

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 with a precise mathematical definition ('vertices whose removal increases the component count'), which is exactly what a cut/articulation vertex is, so an agent knows what it returns in principle. It does not name or contrast any sibling, even though the graph_* family contains near-neighbors like bpj_graph_bridge_links and bpj_graph_weak_components.

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 guidance on when to choose this over related graph tools (bridges, components, boundary nodes), nor any precondition or exclusion beyond the parenthetical definition. The definitional phrasing implies when the result is relevant but does not route the agent among alternatives.

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.