Skip to main content
Glama

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

Tools

Functions exposed to the LLM to take actions

NameDescription
scan_pathA

Scans one file or directory (a skill folder, plugin, hook script, MCP server source or MCP config) for malicious or risky content, such as prompt injection, hidden text, credential theft and data exfiltration. Useful before a skill, plugin or server is installed, enabled or run. Read-only and offline: nothing is executed, written or sent anywhere.

scan_installedA

Scans the agent setup already on this machine, like toolmoat scan with no paths: Claude Code skills, plugins, commands, agents, hooks, settings and user config, Claude Desktop, Cursor, VS Code, Windsurf, Codex and Gemini CLI configs, plus the project files of the server working directory. Read-only and offline.

scan_textA

Scans content passed inline, such as a SKILL.md, an MCP tool description or an MCP config fetched from the web, without writing it to disk. Set kind to say what the content is. Read-only and offline.

list_rulesA

Lists the detection rules toolmoat applies, with id, severity, category, the file kinds each covers, what it detects and how to fix it.

list_pinsA

Shows the MCP servers pinned by toolmoat proxy, how many tools each has pinned and which tool changes are waiting for review. This view is read-only; only the user can accept changes, in a terminal.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 5 tools

Disambiguation5/5

The three scan tools are cleanly separated by input source: installed setup, filesystem path, and inline text. The two list tools are also distinct: pinned MCP servers versus detection rules.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern. The scan_* and list_* prefixes make the tool families predictable.

Tool Count5/5

Five tools is well-scoped for a security scanner: three scan entry points plus two read-only listing tools. Each tool has a clear reason to exist.

Completeness4/5

The surface covers scanning installed setups, individual paths, and inline content, plus rule discovery and pin visibility. Minor gaps exist around detailed pending-change review or accepting changes, but the description indicates acceptance is intentionally user-only in a terminal.

Maintenance

ActivityMaintained
ResponsivenessOutdated data