Skip to main content
Glama

adv_get_version

Retrieve version details for the Adversary MCP Server to verify compatibility and access security features for vulnerability detection and exploit generation.

Instructions

Get server version information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler method _handle_get_version that implements the core logic of the adv_get_version tool. It fetches the version using get_version() from the package __init__ and returns formatted JSON with version, server_type, and domain_layer info.
    async def _handle_get_version(
        self, name: str, arguments: dict
    ) -> list[types.TextContent]:
        """Get server version information."""
        try:
            from adversary_mcp_server import get_version
    
            version_info = {
                "version": get_version(),
                "server_type": "mcp",
                "domain_layer": "enabled",
            }
    
            return [
                types.TextContent(type="text", text=json.dumps(version_info, indent=2))
            ]
    
        except Exception as e:
            logger.error(f"Version check failed: {e}")
            raise CleanAdversaryToolError(f"Version check failed: {str(e)}")
  • The input/output schema definition for the adv_get_version tool in the get_tools() method, specifying no required input parameters.
    Tool(
        name="adv_get_version",
        description="Get server version information",
        inputSchema={"type": "object", "properties": {}},
    ),
  • Registration of the adv_get_version tool in the central tool_dispatcher function within _register_tools(), mapping the tool name to its handler.
    elif name == "adv_get_version":
        return await self._handle_get_version(name, arguments)
  • The helper function get_version() called by the handler to dynamically retrieve the package version, with fallbacks to pyproject.toml parsing and a default constant.
    def get_version() -> str:
        """Get the current version of the adversary-mcp-server package."""
        try:
            return version("adversary-mcp-server")
        except Exception:
            # Fallback - read from pyproject.toml using standard library
            try:
                return _read_version_from_pyproject()
            except Exception:
                # Final fallback to constant if all methods fail
                return DEFAULT_VERSION
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'Get' implies a read operation, the description doesn't disclose any behavioral traits - no information about authentication requirements, rate limits, error conditions, or what format the version information returns. For a tool with zero annotation coverage, this is insufficient disclosure.

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 concise at just three words. It's front-loaded with the essential information - what the tool does - with zero wasted words. Every word earns its place in communicating the core functionality.

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?

For a simple 0-parameter read operation with no output schema, the description is minimally complete. It tells what the tool does but lacks important context about return format, authentication, or differentiation from similar tools. Without annotations or output schema, the agent has incomplete information about what to expect from this 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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already documents this completely. No additional parameter information is needed or provided.

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 'Get server version information' clearly states the verb ('Get') and resource ('server version information'), making the purpose immediately understandable. However, it doesn't distinguish this from sibling tools like 'adv_get_status' - both appear to retrieve server information but for different aspects.

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 siblings like 'adv_get_status' that also retrieve server information, the agent has no indication whether this should be used for version checking, system monitoring, or other contexts. No prerequisites or exclusions are mentioned.

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/brettbergin/adversary-mcp-server'

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