Skip to main content
Glama
FabioDominio

@gnaws/mcp

by FabioDominio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Export Graph

export

Save the scanned resource graph to a file in GEXF, JSON, Markdown, or CSV format for analysis or reporting.

Instructions

Export the resource graph to a file. Requires 'scan' or 'load' to be called first. Supported formats: gexf (Gephi), json (sigma.js viewer), md (markdown report), csv (flat inventory sheet).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoOutput file path. Defaults to graph.gexf, graph.json, report.md, or inventory.csv
formatYesExport format: 'gexf' for Gephi, 'json' for sigma.js viewer, 'md' for markdown report, 'csv' for a flat inventory sheet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / format / description
      Previous value: -"Export format: 'gexf' for Gephi, 'json' for sigma.js viewer, 'md' for markdown report"New value: +"Export format: 'gexf' for Gephi, 'json' for sigma.js viewer, 'md' for markdown report, 'csv' for a flat inventory sheet"
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "gexf",
-  "json",
-  "md"
-]New value: +[
+  "gexf",
+  "json",
+  "md",
+  "csv"
+]
    • changedInput schema / properties / path / description
      Previous value: -"Output file path. Defaults to graph.gexf, graph.json, or report.md"New value: +"Output file path. Defaults to graph.gexf, graph.json, report.md, or inventory.csv"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the prerequisite and supported formats, but doesn't mention side effects like file overwriting or whether the operation is reversible. For an export tool, the write nature is implied, but more detail on behavior (e.g., overwriting, error conditions) would improve transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler. The purpose and prerequisite are front-loaded, and the format list is compact and informative. Every word earns its place.

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 tool with only 2 parameters, a clear prerequisite, and no output schema, the description covers the essential context. It explains the formats and the need for prior scanning/loading. Minor gaps like return behavior or error handling are not critical given the simplicity.

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 coverage is 100%, so baseline is 3. The description adds value by mapping each format to its intended viewer (e.g., gexf for Gephi, json for sigma.js), which goes beyond the schema's descriptions and helps the agent choose the right format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Export' with the resource 'resource graph' and the output to a file, and lists specific formats. It distinguishes itself from siblings like 'detect', 'scan', 'load' by focusing on output, making its purpose unambiguous.

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

Usage Guidelines4/5

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

The description explicitly states a prerequisite ('Requires scan or load to be called first'), which is key usage guidance. It doesn't explicitly mention when not to use it or alternative tools, but the prerequisite provides clear context for appropriate invocation.

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