Skip to main content
Glama
msaad00

agent-bom

by msaad00
OverviewSchemaRelated ServersScoreDiscussions
Python

Graph Export

graph_export
Read-onlyIdempotent

Export agent dependency graphs in formats like GraphML, Cypher, DOT, Mermaid, and JSON for use in security analysis and visualization tools.

Instructions

Export the agent dependency graph in graph-native formats.

    Formats:
    - **graphml** — yEd, Gephi, NetworkX compatible with AIBOM-typed attributes
    - **cypher** — Neo4j import script with AIBOM node labels (AIAgent, MCPServer, Package, Vulnerability)
    - **dot** — Graphviz (pipe through ``dot -Tsvg``)
    - **mermaid** — embed in markdown, GitHub, Notion
    - **json** — machine-readable nodes/edges list

    Returns:
        Graph in the requested format as a string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
config_pathNoPath to MCP config directory. Omit to auto-discover.
formatNoExport format: graphml, cypher, dot, mermaid, or json (default).json

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds valuable context about format compatibility and returns a string, which aligns with idempotentHint. No contradictions.

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?

Well-structured with format list and return description. Two short paragraphs. Could be slightly more concise, but no unnecessary words.

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?

Describes formats, compatibility, and return type (string). No output schema provided, so description fills that gap. Complete for a read-only export tool.

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% for both parameters. Description adds extra meaning by listing format options with their compatibility (e.g., 'yEd, Gephi, NetworkX'), which goes beyond the schema's simple type string.

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?

Clear verb 'Export' + specific resource 'agent dependency graph' + explicit formats. Distinct from siblings like 'context_graph' which likely does something different.

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?

No explicit when-to-use or when-not-to-use guidance. Sibling tools are not referenced. The description implies usage for graph exports but doesn't help choose between formats or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/msaad00/agent-bom'

If you have feedback or need assistance with the MCP directory API, please join our Discord server