Skip to main content
Glama
VMexicano
by VMexicano

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
filtered_shellA

Execute a shell command with intelligent output filtering. Detects command type and applies the optimal filter strategy to reduce token consumption while preserving all actionable information (errors, failures, changes).

filtered_readA

Read a file with intelligent reduction. Modes: "full" (collapses blanks, licenses, imports), "signatures" (extracts declarations only), "relevant" (focus pattern with ±10 lines context).

filtered_grepA

Search for regex patterns in a directory with results grouped by file or match, deduplicated with [×N] prefix. Uses ripgrep when available, falls back to native recursive search.

smart_testA

Execute a test command and return structured, actionable output. Shows only failures by default (name, location, error, expected/received, truncated stack). Detects Jest/Vitest/pytest/cargo-test/go-test automatically.

smart_gitA

Execute git operations with compact, optimized output. Supports: status (compact summary), diff (filtered hunks), log (one-line format), and action commands (commit/push/pull/add/branch with minimal confirmation).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct operation: grep (search), read (file reading), shell (command execution), git (version control), test (test execution). No overlap in purpose.

Naming Consistency3/5

Tools use two different prefixes: 'filtered_' for grep/read/shell and 'smart_' for git/test. While each group is internally consistent, the mix of prefixes reduces overall consistency.

Tool Count5/5

With 5 tools, the server covers essential development operations without being bloated. Each tool serves a clear, non-redundant purpose.

Completeness4/5

The tool set covers search, reading, shell execution, git, and testing—core developer tasks. Minor gaps like file writing or editing are acceptable given the focus on token-efficient inspection.

Maintenance

ActivityMaintained
ResponsivenessNo issues