eLabFTW MCP

expand_links_network

Build a bounded directed link graph around a root eLabFTW experiment or item with BFS, so you can explore incoming and outgoing connections using depth and filter limits.

Instructions

Build the directed link graph around a root experiment/item via BFS. direction is 'both', 'outgoing' or 'incoming'; max_depth is capped at 3; node/edge/fan-out caps and optional filters (allowed_types, category_ids, status_ids, title_regex as JSON arrays/pattern) keep the graph bounded. Returns root, parameters, nodes, edges and truncation flags. Read-only.

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": {
      "root_type": "<root_type>",
      "root_id": "<root_id>"
    },
    "name": "expand_links_network"
  }
}

Input Schema

Name	Required	Default
`root_id`	Yes
`direction`	No	both
`max_depth`	No
`max_edges`	No
`max_nodes`	No
`root_type`	Yes
`status_ids`	No
`include_raw`	No
`title_regex`	No
`category_ids`	No
`max_per_node`	No
`allowed_types`	No
`include_node_summaries`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it declares 'Read-only', discloses hard constraints (max_depth capped at 3, node/edge/fan-out caps), and warns that truncation flags are returned. It omits auth/permission requirements and any rate-limit or pagination behavior.

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?

Dense but front-loaded: purpose, then parameters, then return shape, then safety. No wasted sentences, though the parameter run-on is packed tightly enough to risk being skimmable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter BFS graph tool, the description covers the semantics an agent needs to bound the traversal and interpret return values (an output schema exists, so return details need not be exhaustive). The unaddressed include_raw/include_node_summaries flags and absent auth notes are the remaining shortfalls.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does for most parameters: direction values, the depth cap, the node/edge/fan-out caps, and the allowed_types/category_ids/status_ids/title_regex filters are all explained with their JSON-array/pattern format. It leaves include_raw, include_node_summaries, root_type, and root_id unexplained, which is a real but partial gap.

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 ('Build the directed link graph') and resource, plus the algorithm (BFS) and scope (around a root experiment/item). This clearly distinguishes it from the sibling get_entity_links, though the sibling is never named explicitly.

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?

Usage is implied by 'around a root experiment/item via BFS' – an agent can infer this is for multi-hop traversal. However, it never says when to use this versus get_entity_links or get_item, and gives no exclusions or prerequisites.

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