Skip to main content
Glama
wagonbomb

Megaraptor MCP

by wagonbomb

get_client_info

Retrieve detailed endpoint information including hardware specifications, operating system details, and network addresses from the Velociraptor forensics platform to support incident response investigations.

Instructions

Get detailed information about a specific Velociraptor client.

Args: client_id: The client ID (e.g., 'C.1234567890abcdef')

Returns: Detailed client information including hardware, OS, IP addresses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_client_info tool is implemented here as an asynchronous function decorated with @mcp.tool(). It validates input, queries the Velociraptor client via VQL, and formats the output, including error handling.
    async def get_client_info(client_id: str) -> list[TextContent]:
        """Get detailed information about a specific Velociraptor client.
    
        Args:
            client_id: The client ID (e.g., 'C.1234567890abcdef')
    
        Returns:
            Detailed client information including hardware, OS, IP addresses.
        """
        try:
            # Validate client_id
            client_id = validate_client_id(client_id)
    
            client = get_client()
    
            vql = f"SELECT * FROM clients(client_id='{client_id}')"
            results = client.query(vql)
    
            if not results:
                return [TextContent(
                    type="text",
                    text=json.dumps({
                        "error": f"Client {client_id} not found",
                        "hint": "Use list_clients tool to find valid client IDs"
                    })
                )]
    
            # Return the full client info
            return [TextContent(
                type="text",
                text=json.dumps(results[0], indent=2, default=str)
            )]
    
        except ValueError as e:
            # Validation errors
            return [TextContent(
                type="text",
                text=json.dumps({
                    "error": str(e),
                    "hint": "Provide a valid client ID starting with 'C.'"
                })
            )]
    
        except grpc.RpcError as e:
            # gRPC errors
            error_info = map_grpc_error(e, f"fetching client {client_id}")
            return [TextContent(
                type="text",
                text=json.dumps(error_info, indent=2)
            )]
    
        except Exception:
            # Generic errors - don't expose internals
            return [TextContent(
                type="text",
                text=json.dumps({
                    "error": "Failed to get client information",
                    "hint": "Check Velociraptor server connection and try again"
                })
            )]
Behavior3/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. It discloses the nature of the return value ('Detailed client information including hardware, OS, IP addresses'), which is helpful context. However, it does not explicitly confirm this is a read-only/safe operation, mention error states, or disclose any latency/caching behavior expected for this lookup.

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 uses a clean docstring-style structure with 'Args:' and 'Returns:' sections. Every sentence earns its place: the first states purpose, the second documents the parameter with an example, and the third summarizes the return data. No extraneous text is present.

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

Completeness5/5

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

Given this is a simple single-parameter lookup tool with an existing output schema (per context signals), the description is complete. It covers the tool's purpose, the single required input with an example, and summarizes the return data sufficiently without needing to replicate the full output schema structure.

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?

With 0% schema description coverage, the description successfully compensates by documenting the 'client_id' parameter with a concrete example format ('C.1234567890abcdef'). This adds critical semantic meaning missing from the schema. It would achieve a 5 if it also explained where to obtain this ID or described the format constraints (e.g., that it starts with 'C.').

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 uses a specific verb ('Get') and clearly identifies the resource ('detailed information about a specific Velociraptor client'). The word 'specific' effectively distinguishes this tool from the sibling 'list_clients' tool, indicating it retrieves data for one identified endpoint rather than enumerating many.

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 implies usage by requiring a 'client_id' argument, suggesting it should be used when a specific client identifier is already known. However, it does not explicitly state when to use this versus 'list_clients' (e.g., 'use after identifying a client ID from list_clients') or mention any prerequisites or exclusions.

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/wagonbomb/megaraptor-mcp'

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