Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_server_config

Retrieve current server configuration details like API URL, version, and connection status to verify setup and connectivity for threat analysis operations.

Instructions

Get current server configuration including API URL and connection status.

Returns: Configuration details including API URL, version, and status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The get_server_config tool handler: an async function decorated with @app.tool that returns the server configuration dictionary, including API URL, version, API key status, connection test result, and workspace info if connected.
    @app.tool
    async def get_server_config() -> Dict[str, Any]:
        """
        Get current server configuration including API URL and connection status.
        
        Returns:
            Configuration details including API URL, version, and status
        """
        config = {
            "api_url": API_BASE_URL,
            "version": "0.1.0",
            "api_key_configured": bool(API_KEY and len(API_KEY) > 10)
        }
        
        # Test connection if API key is available
        if config["api_key_configured"]:
            try:
                user_info = await get_client().get("/public-api/me")
                config["connection_status"] = "connected"
                config["workspace"] = user_info.get("userInfo", {}).get("workspace", {}).get("name", "Unknown")
            except Exception as e:
                config["connection_status"] = "failed"
                config["error"] = str(e)
        else:
            config["connection_status"] = "no_api_key"
        
        return config
  • The @app.tool decorator registers the get_server_config function as an MCP tool.
    @app.tool
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions what the tool returns but lacks details on permissions, rate limits, error handling, or whether it's a read-only operation. For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is concise and front-loaded, with the first sentence stating the core purpose and the second elaborating on returns. There's minimal waste, though the 'Returns:' section could be integrated more smoothly into a single sentence for better flow.

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 that the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is adequate but incomplete. It specifies what configuration details are included but doesn't address behavioral aspects like safety or performance, which are important for a server configuration tool with no annotations.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the return values, which aligns with the baseline expectation for tools without inputs.

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's purpose with a specific verb ('Get') and resource ('current server configuration'), and specifies what it includes ('API URL and connection status'). However, it doesn't explicitly differentiate from sibling tools like 'get_statuses' or 'get_submission_config_extractor', which might have overlapping scopes, preventing a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools that might retrieve configuration or status-related data (e.g., 'get_statuses', 'get_submission_config_extractor'), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage.

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/threat-zone/threatzonemcp'

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