Skip to main content
Glama
wagonbomb

Megaraptor MCP

by wagonbomb

get_artifact

Retrieve complete Velociraptor artifact definitions including parameters, sources, and VQL for digital forensics and incident response investigations.

Instructions

Get the full definition of a Velociraptor artifact.

Args: artifact_name: The name of the artifact (e.g., 'Windows.System.Pslist')

Returns: Complete artifact definition including parameters, sources, and VQL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artifact_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the `get_artifact` tool which retrieves the full definition of a Velociraptor artifact using a VQL query.
    @mcp.tool()
    async def get_artifact(artifact_name: str) -> list[TextContent]:
        """Get the full definition of a Velociraptor artifact.
    
        Args:
            artifact_name: The name of the artifact (e.g., 'Windows.System.Pslist')
    
        Returns:
            Complete artifact definition including parameters, sources, and VQL.
        """
        try:
            # Validate artifact_name
            if not artifact_name or not artifact_name.strip():
                return [TextContent(
                    type="text",
                    text=json.dumps({
                        "error": "Artifact name cannot be empty",
                        "hint": "Use list_artifacts tool to find available artifacts"
                    })
                )]
    
            client = get_client()
    
            vql = f"SELECT * FROM artifact_definitions(names='{artifact_name}')"
            results = client.query(vql)
    
            if not results:
                return [TextContent(
                    type="text",
                    text=json.dumps({
                        "error": f"Artifact '{artifact_name}' not found",
                        "hint": "Use list_artifacts tool to find available artifacts"
                    })
                )]
    
            artifact = results[0]
    
            # Format the output
            formatted = {
                "name": artifact.get("name", ""),
                "description": artifact.get("description", ""),
                "type": artifact.get("type", ""),
                "author": artifact.get("author", ""),
                "parameters": artifact.get("parameters", []),
                "sources": artifact.get("sources", []),
                "precondition": artifact.get("precondition", ""),
                "required_permissions": artifact.get("required_permissions", []),
            }
    
            return [TextContent(
                type="text",
                text=json.dumps(formatted, indent=2, default=str)
            )]
    
        except grpc.RpcError as e:
            # gRPC errors
            error_info = map_grpc_error(e, f"fetching artifact '{artifact_name}'")
            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 artifact definition",
                    "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 provided, so description carries full disclosure burden. It successfully describes the output structure ('parameters, sources, and VQL'), but omits operational details like read-only safety, caching behavior, or error cases (e.g., artifact not found).

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?

Uses efficient docstring format (Args/Returns) with zero wasted words. Three sentences cover purpose, parameter format, and return value structure. Front-loaded with the core action immediately stated.

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?

Appropriate for a single-parameter retrieval tool with output schema. The description explains what the return value contains (parameters, sources, VQL), compensating for unseen output schema details. Could benefit from mentioning read-only nature, but adequate for complexity level.

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 has 0% description coverage. The description compensates effectively with a concrete example ('Windows.System.Pslist') that clarifies the dot-notation naming convention expected for artifact_name, adding essential semantic context missing from the schema.

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 specific verb ('Get') with specific resource ('full definition of a Velociraptor artifact'). Distinguishes from sibling 'collect_artifact' (which executes artifacts) and 'list_artifacts' (which lists names only) by emphasizing 'definition' retrieval.

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?

No explicit guidance on when to use this tool versus alternatives like 'list_artifacts' (to browse available artifacts) or 'collect_artifact' (to execute data collection). Lacks workflow context for the retrieval step.

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