Skip to main content
Glama

Directed Euler trail feasibility

bpj_graph_euler_trail
Read-onlyIdempotent

Use connectivity and degree balances to determine if a directed trail can traverse each edge once.

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

Input Schema

NameRequiredDescriptionDefault
graphYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds the high-level algorithmic basis, but it does not say what the result looks like, how malformed graphs are handled, or what complexity to expect.

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?

The definition is a single front-loaded sentence with no wasted wording. It is concise, though the brevity leaves gaps in actionable detail rather than fully earning its place.

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 graph-feasibility tool with a structured JSON input and no output schema, the description should clarify both the input format and the return value. It omits the adjacency-map structure and does not say whether the result is a boolean, a certificate, or a reason for failure.

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 required parameter is a string named graph with a schema title "Directed adjacency map (JSON)" but 0% schema description coverage. The description never explains the expected JSON shape, edge direction semantics, or limits such as the 6000-character maximum, so it adds little meaning beyond the schema.

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 gives a specific verb and resource: determine whether a directed trail can traverse every edge once. That is clearly an Euler-trail feasibility check, but it does not distinguish this from neighboring graph-analysis tools such as cycle detection or reachability tools.

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 tool versus the many sibling graph tools, nor any when-not conditions. "Use connectivity and degree balances" describes the method rather than when an agent should call it, leaving usage implied only by the tool name and purpose.

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.