Skip to main content
Glama

Test a graph bipartition

bpj_graph_bipartition
Read-onlyIdempotent

Treat links as undirected and attempt to assign opposite groups to neighbors.

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

Input Schema

NameRequiredDescriptionDefault
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact that annotations cannot convey: edge direction is ignored even though the schema calls the input a directed adjacency map. It still omits what happens on failure (e.g., whether a conflicting edge or odd cycle is reported) and says nothing about the returned value.

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 short, front-loaded sentence with no filler or repeated information. Its brevity is appropriate in form, though it edges toward under-specification rather than tight communication.

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 tool with no output schema, one undocumented parameter, and a non-obvious return concept (boolean verdict, node-to-group assignment, or witness), the description should say what comes back and how to read it. None of that is present, leaving the agent unable to interpret a result or craft a valid argument from the definition alone.

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?

There is a single parameter with 0% schema description coverage, so the description carries the burden of explaining it and does not. It never states that the argument is a JSON object mapping nodes to neighbor lists, what key/value types are expected, or what the 6000-character limit implies about graph size.

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 describes the operation as assigning opposite groups to neighbors on an undirected view of the links, which implies a bipartiteness/2-coloring check. However, it never states the actual purpose in outcome terms (deciding whether the graph is bipartite, or producing a partition), so an agent must infer the result from the name and title. It also does not distinguish it from graph-analysis siblings such as bpj_graph_cycle_witness or 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?

"Treat links as undirected" is a scope note about how input is interpreted, not guidance about when to choose this tool. There is no statement of prerequisites, no when-not condition, and no pointer to a related sibling for adjacent graph questions.

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.