Skip to main content
Glama
IrMaho

Antigravity Base MCP Server

by IrMaho

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_LOG_LEVELNoLogging level for the MCP server (e.g. 'info'). This is used in client configuration examples.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
echoA

Echoes back the input message with optional repetition and prefix formatting.

get_system_infoA

Retrieves current system diagnostics including OS, Node version, memory, and CPU info.

my_custom_toolD

Detailed description of what this tool accomplishes, its expected input, and its output format.

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_code_snippetGenerates a structured prompt to perform deep code analysis, security audit, and refactoring

Resources

Contextual data attached and managed by the client

NameDescription
Server Status & HealthCurrent runtime configuration and server health status

TDQS

C2.5/5.0

Scored across 3 tools

Disambiguation4/5

echo and get_system_info are clearly distinct operations, and my_custom_tool is not described in a way that directly overlaps with them. However, the placeholder description for my_custom_tool leaves its actual purpose ambiguous, so the set is not perfectly unambiguous.

Naming Consistency2/5

The naming is inconsistent: echo uses a bare verb, get_system_info follows verb_noun, and my_custom_tool uses a vague custom label. There is no shared naming convention across the three tools.

Tool Count3/5

Three tools is not an unreasonable number by itself, but the set feels like a minimal scaffold rather than a focused server. The unrelated utilities and placeholder custom tool make the count less defensible than it would be with a clear shared purpose.

Completeness2/5

The server lacks a coherent domain, so it is difficult to determine what complete coverage would look like. echo and get_system_info are isolated utilities, while my_custom_tool is an unspecified placeholder, leaving obvious gaps in any implied workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues