Skip to main content
Glama

export_networks

Export S3-based bibliometric networks as node/edge CSVs for Neo4j/igraph and GraphML for Gephi, covering one-mode, two-mode, and knowledge graph outputs.

Instructions

Export the networks behind S3 at three levels: one-mode (papers tied by S3 similarity and/or citations), two-mode (papers + authors, keywords, journals, institutions, countries, funders or references) and a knowledge graph (all node and tie types together, with communities as nodes). Writes node/edge CSVs (Neo4j, igraph) and GraphML (Gephi) to output_dir (default: the run folder) and returns the files and a summary of what each network contains.

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": {
      "run_id": "<run_id>"
    },
    "name": "export_networks"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
output_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

A3.7/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 disclose the key side effect: it writes node/edge CSVs and GraphML files to output_dir, with the run folder as default, and returns file paths plus a per-network summary. It does not say whether existing files are overwritten or what happens on invalid run_id, which are the remaining behavioral gaps.

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 dense but well-ordered sentence: the three export levels come first, then the write destination, then the return payload. Every clause carries information, though the enumeration of node types is somewhat list-heavy.

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?

An output schema exists, so return values need not be elaborated, and the write target and defaults are covered. The one meaningful omission for a two-param tool is the semantics of run_id and any precondition that the run has completed S3 analysis.

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 0%, so the description must compensate. It explains output_dir well (what is written and the run-folder default), but run_id — the sole required parameter — is never defined or linked to a prior analysis run.

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 (export) and resource (networks behind S3) and enumerates the three export levels concretely, so an agent knows exactly what artifact it produces. It does not, however, distinguish itself from export_results or build_report, so sibling differentiation is left to inference.

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 rather than stated: the Gephi/Neo4j/igraph formats hint that this is the tool for downstream network visualization. There is no explicit when-to-use, no statement that an S3 analysis run must already exist, and no contrast with export_results.

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