Skip to main content
Glama
Sign In
MCP Context Graph

MCP Context Graph

by padobrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

debug_dump_graph

Dump the entire graph structure to Mermaid, JSON, or Graphviz DOT for visualization, enabling quick debugging and clear understanding of relationships.

Instructions

DEBUG: Dump the entire graph structure for visualization. Returns the graph in Mermaid diagram, JSON, or Graphviz DOT format. Useful for debugging and understanding the graph structure.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "debug_dump_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: 'mermaid' for Mermaid flowchart diagram, 'json' for raw structure with all node/edge data, 'dot' for Graphviz DOT format.mermaid
show_edgesNoInclude edge relationships in output.
limit_nodesNoMaximum nodes to include in output (for large graphs). Set to null/None to include all nodes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It claims to 'Dump the entire graph structure' but the schema reveals a default limit of 50 nodes (limit_nodes), contradicting the 'entire' claim. Additionally, it does not note potential performance issues or truncation behavior for large 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?

The description is two sentences, front-loaded with the DEBUG prefix and a clear action. Every word earns its place, and it effectively communicates the purpose without unnecessary filler.

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?

The description mentions return formats, which is helpful given no output schema. However, it fails to explain the default node limit that contradicts the 'entire graph' phrase, which is critical for understanding potential truncation. This omission makes it incomplete for a tool with a configurable limit.

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

Parameters3/5

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

Schema descriptions cover 100% of the parameters with detailed explanations (e.g., format, show_edges, limit_nodes). The description adds minimal semantic value beyond repeating the output formats ('Mermaid diagram, JSON, or Graphviz DOT format'), so the baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool's function: 'Dump the entire graph structure for visualization.' The verb 'dump' and resource 'graph structure' are specific, and the DEBUG prefix distinguishes it from sibling tools like find_symbol or get_context, which focus on focused code navigation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context with 'Useful for debugging and understanding the graph structure,' indicating when to use this tool. However, it does not explicitly exclude any alternatives or mention sibling tools, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools