| create_graph | Create a new knowledge graph. Supports multiple graph types such as topology, timeline, changelog, requirement documentation, etc. Design guidelines for each graph type: topology: Used to represent dependencies between system components and modules. Recommended to first create main module nodes, then add component nodes, and finally represent relationships through edges like calls, dependencies, and containment timeline: Used to record important project events and decisions. Recommended to add event nodes in chronological order and link related personnel and decisions changelog: Used to track change history of features and components. Recommended to create nodes for each significant change, marking change types and impact scope requirement: Used for requirement management and tracking. Recommended to first create high-level requirements, then break down into specific features, and finally link to responsible persons and iterations knowledge_base: Used to build domain knowledge systems. Recommended to start from core concepts and gradually expand related concepts and relationships ontology: Used for formal representation of domain concepts and relationships, suitable for building standardized knowledge models
|
| add_node | Add a node to the knowledge graph. Nodes are the basic units of the graph, and different types of graphs support different types of nodes.
Use cases: Create component or module nodes in topology graphs Add event or decision nodes in timeline graphs Create requirement or feature nodes in requirement documents Build concept hierarchies in knowledge bases
Usage recommendations: First create the graph using create_graph Select the appropriate node type based on graph type Provide meaningful names and descriptions Link related files when applicable Add metadata for additional structured information
Return data: |
| add_edge | Add edges in the knowledge graph, connecting two nodes to build a relationship network. Edges represent relationship types between nodes, such as dependencies, containment, associations, etc.
Prerequisites: Must first create a graph (using create_graph) Source and target nodes must already exist Edge type must match the graph type
Usage recommendations: First use list_graphs to get graph and node information Confirm both source and target nodes exist and their types match Choose appropriate edge type based on graph type Add meaningful labels to edges to help understand relationships If relationships have varying strengths, use the weight parameter
Return data: |
| publish_graph | Publish a knowledge graph, changing its status from draft to published. Published graphs can still be modified, but it's recommended to track important changes through version management.
Prerequisites: Graph must exist and be in draft status Recommended to ensure graph content is complete before publishing Ensure all necessary nodes and edges have been added
Usage recommendations: First use list_graphs to check the current status of the graph Use get_node_details to check the completeness of key nodes Review the graph structure before publishing Record publication time for version management Notify relevant team members after publication
Return data: |
| list_graphs | List all knowledge graphs with support for filtering by status and type. This is the main tool for getting information about existing graphs and an important path for obtaining node IDs.
Use cases: View all available graphs and their basic information Get the node list of a specific graph for subsequent edge addition or node detail queries Filter graphs by status, such as viewing all drafts or published graphs Filter graphs by type, such as viewing only topology or timeline graphs
Usage recommendations: First call this tool to get the graph list and node information Get the required graph ID and node ID from the returned data Use these IDs to call other tools (like add_edge, get_node_details) Recommended to use this tool to confirm the target graph's status before performing any node or edge operations
Return data: |
| get_node_details | Get detailed information about a specific node in the graph. This tool must be used in conjunction with the list_graphs tool, as the nodeId must be obtained from the list_graphs response.
Use cases: View complete node attributes Check associated resources (SVG/Markdown) Analyze node relationships with others Check current state before modifying a node
Usage recommendations: First call list_graphs to get the node list of the target graph Get the required nodeId from the returned nodes array Use the obtained graphId and nodeId to call this tool Check the returned relationship data to determine if further action is needed
Return data: data: Node details id: Node ID name: Node name type: Node type description: Node description filePath: Associated file path metadata: Node metadata resources: Associated resource list relationships: Relationship list
|
| get_creation_guidelines | Get creation guidelines and standards for SVG graphics and Markdown documents. This tool is a prerequisite for the save_resource tool and must be called before creating and saving any resources.
Use cases: Get drawing standards before creating SVG visualizations Get format requirements before creating Markdown documents Get complete guidelines before batch resource creation
Usage recommendations: Call this tool before starting any resource creation Carefully read and follow the naming rules and directory structure Create resources according to guidelines, then use save_resource tool Recommended to save guidelines for team reference
Return data: data: Guidelines content guidelines: Guidelines text content type: Guidelines type (svg/markdown/all) version: Guidelines version
|
| save_resource | Save AI-generated SVG graphics or Markdown documents to the knowledge graph. This tool must be used in conjunction with get_creation_guidelines and list_graphs tools.
Use cases: Save SVG visualization representation of the graph Save Markdown documents related to nodes Batch save multiple resource files
Usage recommendations: First call get_creation_guidelines to get resource creation standards Use list_graphs to get target graph ID and node ID (if needed) Create resource content according to standards Use this tool to save the resource After saving, use get_node_details to check resource association status
Return data: |
| update_node | Modify nodes in the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools.
Use cases: Update basic node information (name, description, etc.) Update file paths associated with nodes Update node metadata information
Usage recommendations: First call list_graphs to get target graph and node ID Use get_node_details to check current node status Only update fields that need to be modified, keep others unchanged After updating, call get_node_details again to confirm changes
Return data: |
| update_edge | Modify edges in the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools.
Use cases: Update edge label information Adjust edge weight values Update edge metadata information
Usage recommendations: First call list_graphs to get target graph information Use get_node_details to view edge list of related nodes Only update fields that need to be modified, keep others unchanged After updating, call get_node_details again to confirm changes
Return data: |
| delete_node | Delete nodes from the knowledge graph. This tool must be used in conjunction with list_graphs tool, and the operation cannot be undone.
Use cases: Delete incorrectly created nodes Delete nodes that are no longer needed Delete redundant nodes when restructuring the graph
Usage recommendations: First call list_graphs to get target graph and node information Use get_node_details to check node's associated resources and relationships Confirm deletion won't affect other important nodes Set confirmDelete to true to confirm deletion Recommended to backup important data before deletion
Important notes: Deleting a node will also delete all edges related to that node If the node has associated resources, they won't be deleted but will be unlinked
Return data: data: Deletion result id: Deleted node ID name: Node name type: Node type deletedAt: Deletion time
|
| delete_edge | Delete edges from the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools, and the operation cannot be undone.
Use cases: Delete incorrectly created relationships Update relationship structure between nodes Clean up redundant relationships when restructuring the graph
Usage recommendations: First call list_graphs to get target graph information Use get_node_details to get edge details Confirm deletion won't break important relationship structures Set confirmDelete to true to confirm deletion
Important notes: Return data: data: Deletion result id: Deleted edge ID deletedAt: Deletion time
|
| update_resource | Update resource information in the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools.
Use cases: Modify resource title or description Update resource metadata information Improve resource documentation
Usage recommendations: First call list_graphs to get target graph information Use get_node_details to check current resource information Only update fields that need to be modified Maintain consistency in resource naming
Return data: |
| delete_resource | Delete resources from the knowledge graph. This tool must be used in conjunction with list_graphs and get_node_details tools, and the operation cannot be undone.
Use cases: Delete outdated resource files Clean up unnecessary documents Remove incorrectly created resources
Usage recommendations: First call list_graphs to get target graph information Use get_node_details to confirm resource associations Confirm deletion won't affect other nodes Set confirmDelete to true to confirm deletion Recommended to backup important resources before deletion
Important notes: Deleting a resource will also delete the physical file Will automatically unlink from all nodes This operation cannot be recovered
Return data: data: Deletion result id: Deleted resource ID type: Resource type deletedAt: Deletion time
|
| unlink_resource | Unlink resource associations from nodes. This tool must be used in conjunction with list_graphs and get_node_details tools.
Use cases: Adjust resource associations Remove incorrect resource associations Reorganize node resource structure
Usage recommendations: First call list_graphs to get target graph information Use get_node_details to view node's resource associations Confirm unlinking won't affect other functionality Record changes for potential re-association
Important notes: Only removes association, does not delete resource Resource can still be used by other nodes Association can be re-established at any time
Return data: |
