Skip to main content
Glama
r3-yamauchi

MCP Configuration Editor

by r3-yamauchi

export_config

Export the complete MCP server configuration as JSON for backup, sharing, or migration purposes.

Instructions

MCP設定全体をJSON形式でエクスポートする。

現在の設定を表示や別の場所へのコピー用に取得します。

Returns:
    Dict[str, Any]: 設定全体と設定ファイルパスを含む辞書
        - config: 現在の設定の完全な内容
        - config_path: 設定ファイルのパス

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'export_config' tool. It loads the current MCP configuration using load_config() and returns it as a dictionary along with the configuration file path. Registered via @mcp.tool decorator.
    @mcp.tool(name="export_config")
    async def export_config() -> Dict[str, Any]:
        """MCP設定全体をJSON形式でエクスポートする。
    
        現在の設定を表示や別の場所へのコピー用に取得します。
    
        Returns:
            Dict[str, Any]: 設定全体と設定ファイルパスを含む辞書
                - config: 現在の設定の完全な内容
                - config_path: 設定ファイルのパス
        """
        config = load_config()
    
        return {"config": config.model_dump(exclude_none=True), "config_path": str(CONFIG_PATH)}
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 of behavioral disclosure. It describes what the tool does (exports configuration) and what it returns, but doesn't mention important behavioral aspects like whether this requires special permissions, if it's a read-only operation, potential rate limits, or how large configurations are handled. It provides basic context but lacks comprehensive behavioral details.

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?

The description is perfectly structured and concise: a clear purpose statement, a usage context sentence, and a detailed return value specification. Every sentence earns its place, with no redundant information. The Japanese text is efficiently translated in the response format.

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

Completeness3/5

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

Given the tool has no parameters, no annotations, and no output schema, the description does a reasonable job explaining what the tool returns. However, for a configuration export tool, it could benefit from mentioning whether this includes sensitive data, if the export is in a specific format version, or any limitations on what can be exported. The description is adequate but has clear gaps in contextual information.

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?

The tool has zero parameters, so the baseline score is 4. The description appropriately doesn't waste space discussing non-existent parameters, and the 100% schema description coverage for the empty schema is irrelevant since there are no parameters to document.

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?

The description clearly states the tool exports the entire MCP configuration in JSON format, which is a specific verb (export) + resource (MCP configuration). However, it doesn't explicitly differentiate from sibling tools like 'get_server' or 'validate_config' which might also retrieve configuration data, so it doesn't reach the highest score.

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?

The description provides implied usage context ('for display or copying to another location'), but doesn't explicitly state when to use this tool versus alternatives like 'get_server' for specific server configurations or 'validate_config' for validation purposes. No explicit exclusions or alternative tool recommendations are provided.

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/r3-yamauchi/mcp-conf-mcp-server'

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