Skip to main content
Glama
Sign In
code-explorer

code-explorer

by vmikhailov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

ingest_graph_data

Batch ingest custom nodes and relationships into the architecture graph database to extend code-explorer's index with domain-specific entities and their connections.

Instructions

Batch ingest custom nodes and relationships into the graph database.

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": {
      "nodes": "<nodes>"
    },
    "name": "ingest_graph_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodesYesYAML list of node objects.
relationshipsNoOptional YAML list of relationship objects.
workspacePathNoOptional workspace root path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.80.5

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for a mutating tool and does not meet it. It never says whether nodes/relationships are merged or overwritten on duplicate IDs, whether the operation is idempotent or transactional, what happens on partial failure, or what permissions are needed. "Batch" implies bulk semantics but nothing about atomicity or limits.

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?

A single front-loaded sentence with no filler, and the key concept (batch ingest of custom graph data) lands immediately. Its brevity is efficient rather than padded, though it borders on under-specified for a write operation.

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 three-parameter mutation tool with no annotations and no output schema, the description should cover merge/conflict behavior and what the call returns (e.g., counts ingested or errors). Neither is addressed, leaving the agent unable to predict the side effects of a call it is about to make.

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 coverage is 100%, so nodes/relationships/workspacePath are already documented as YAML lists and an optional workspace root. The description adds only the notion of batching and custom (non-derived) entities; it says nothing about expected YAML field shapes or how workspacePath affects ingestion scope.

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?

States a specific verb and resource: batch-ingesting custom nodes and relationships into the graph database. It is clearly distinguishable from the read-side sibling execute_custom_read_cypher by the write/ingest framing. It stops short of naming or contrasting any sibling explicitly.

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 when-to-use or when-not-to-use guidance, and no prerequisites such as needing an initialized workspace (init_workspace exists). The word "custom" hints this is for user-defined schema extensions rather than extracted code entities, but that inference is left to the agent.

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