Skip to main content
Glama
111-test-111

Math MCP Server

by 111-test-111

graph_theory_suite

Perform graph theory analyses including shortest path, centrality, community detection, and more. Accepts edge lists or adjacency matrices.

Instructions

Brief description: Professional graph theory analysis tool, supporting shortest path, maximum flow, connectivity analysis, centrality calculation, community detection, spectral analysis, and other comprehensive graph theory functions.

Examples:
    graph_theory_suite(operation='shortest_path', edge_list=[[1,2], [2,3], [1,3]], source_node=1, target_node=3)
    graph_theory_suite(operation='centrality_analysis', graph_data={'nodes': [1,2,3], 'edges': [[1,2], [2,3]]})
    graph_theory_suite(operation='graph_visualization', adjacency_matrix=[[0,1,1],[1,0,1],[1,1,0]], filename='graph_plot')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesGraph theory operation type. Supports: 'shortest_path', 'all_pairs_shortest_path', 'maximum_flow', 'connectivity_analysis', 'centrality_analysis', 'community_detection', 'spectral_analysis', 'graph_properties', 'minimum_spanning_tree', 'graph_coloring', 'clique_analysis', 'graph_visualization', 'graph_comparison', 'graph_generation'
graph_dataNoGraph data dictionary. Format: {'nodes': [list of nodes], 'edges': [list of edges]}
adjacency_matrixNoAdjacency matrix. Square matrix, elements represent connection weights between nodes
edge_listNoEdge list. Format: [[source_node, target_node], ...] or with weights
node_listNoNode list. Used to specify node identifiers
source_nodeNoSource node for algorithms like shortest path
target_nodeNoTarget node for algorithms like shortest path
weight_attributeNoWeight attribute name for weighted graph algorithmsweight
directedNoWhether it is a directed graph
algorithmNoAlgorithm type. E.g., 'dijkstra', 'bellman_ford' for shortest pathauto
k_valueNoK value for K-means clustering, K-core analysis
thresholdNoThreshold value for filtering edges or nodes
layoutNoGraph layout algorithm. Supports: 'spring', 'circular', 'random'spring
filenameNoSave filename without path
node_colorsNoList of node colors for visualization
edge_colorsNoList of edge colors for visualization
node_sizesNoList of node sizes for visualization
show_labelsNoWhether to show node labels in visualization
figsizeNoFigure size for visualization
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose any behavioral traits such as side effects, authentication needs, rate limits, or computational intensity. The description is purely functional.

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 description is concise and includes a brief overview followed by three examples. No extraneous text; information is front-loaded.

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 19 parameters and no output schema, the description is incomplete. It does not explain what each operation returns, how parameters interact, or provide guidance on selecting the right algorithm. The examples help but are insufficient for full understanding.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds examples that demonstrate parameter usage, but does not add significant semantic depth 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 clearly states it is a 'professional graph theory analysis tool' supporting a list of common operations, which makes the purpose clear. However, it does not differentiate from sibling tools, though none are graph-related.

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

Usage Guidelines3/5

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

The description provides examples but does not explicitly state when to use this tool versus alternatives or when not to use it. Usage is implied by the tool's name and the listed operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/111-test-111/math-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server