Pythagraph RED MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_graph_dataB | Retrieve detailed graph data from Pythagraph RED API. Returns comprehensive information including nodes, edges, statistics, and metadata formatted as tables and descriptions. Perfect for analyzing graph structure and getting detailed insights. |
| get_graph_summaryA | Get a concise summary of graph data from Pythagraph RED API. Provides overview statistics, node/edge type distributions, and key insights without overwhelming detail. Use includeDetails=true for more comprehensive analysis. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have distinct purposes: get_graph_data provides detailed, comprehensive graph data, while get_graph_summary offers a concise overview. However, the inclusion of an includeDetails parameter in get_graph_summary could cause some overlap or confusion, as it blurs the line between summary and detailed data retrieval.
Both tools follow a consistent verb_noun pattern (get_graph_data and get_graph_summary), using snake_case and the same verb 'get'. This makes them predictable and easy to understand, with no deviations in naming style.
With only 2 tools, the server feels thin for a graph analysis domain, as it lacks essential operations like creating, updating, or deleting graph data. This limited scope may hinder agents from performing full workflows, making it inappropriate for comprehensive graph management.
The server is severely incomplete for graph analysis, covering only retrieval operations (detailed and summary). There are significant gaps, such as no tools for creating, modifying, or deleting graphs, which are core to graph lifecycle management and will likely cause agent failures in broader tasks.