Skip to main content
Glama
runtimeguard

runtime-guard

Official

server_info

Retrieve runtime identity details such as build ID, active workspace root, and resolved base directory for this AIRG server instance.

Instructions

Return runtime identity details for this AIRG server instance.

Includes build id, active workspace root, and resolved base directory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the server_info tool. It activates the runtime context, retrieves SERVER_BUILD, WORKSPACE_ROOT, and BASE_DIR, and returns an info string.
    def server_info(ctx: Context | None = None) -> str:
        """Return runtime identity details for this AIRG server instance.
    
        Includes build id, active workspace root, and resolved base directory.
        """
        tokens = activate_runtime_context(ctx)
        from config import BASE_DIR
        try:
            return f"ai-runtime-guard build={SERVER_BUILD} workspace={WORKSPACE_ROOT} base_dir={BASE_DIR}"
        finally:
            reset_runtime_context(tokens)
  • src/server.py:21-31 (registration)
    The server_info function is registered as an MCP tool via mcp.tool()(tool) in the registration loop.
    for tool in [
        server_info,
        restore_backup,
        execute_command,
        read_file,
        write_file,
        edit_file,
        delete_file,
        list_directory,
    ]:
        mcp.tool()(tool)
  • server_info is re-exported from the tools package via __init__.py.
    from .command_tools import execute_command, server_info
    from .file_tools import delete_file, edit_file, list_directory, read_file, write_file
    from .restore_tools import restore_backup
    
    __all__ = [
        "server_info",
        "execute_command",
        "read_file",
        "write_file",
  • server_info is listed in the AIRG_MCP_TOOLS constant used for config management.
    AIRG_MCP_TOOLS = [
        "server_info",
        "restore_backup",
        "execute_command",
        "read_file",
        "write_file",
        "edit_file",
        "delete_file",
        "list_directory",
    ]
  • src/server.py:6-15 (registration)
    server_info is imported from tools in the MCP server entrypoint.
    from tools import (
        delete_file,
        edit_file,
        execute_command,
        list_directory,
        read_file,
        restore_backup,
        server_info,
        write_file,
    )
Behavior4/5

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

No annotations are provided, so the description carries the burden. It clearly indicates a read-only operation ('Return... details'), with no mention of side effects or prerequisites. It could add explicit safety assurance.

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?

Two sentences: first states the purpose, second lists the details returned. Every sentence adds value, front-loaded with the main action.

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?

For a simple informational tool with no required parameters and an output schema, the description is adequate. It lists key return fields, though it could mention it is safe to call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter 'ctx' has no description in the schema and is not mentioned in the description. With 0% schema description coverage, the description should compensate but does not explain the parameter's purpose or usage.

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?

Description clearly states it 'Return runtime identity details' for the AIRG server instance, including build id, workspace root, and base directory. This distinguishes it from siblings which are all action-oriented tools (delete, edit, etc.).

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?

Description does not explicitly state when to use this tool vs alternatives, but the context implies it is for retrieving server metadata. No exclusions or alternative suggestions 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/runtimeguard/runtime-guard'

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