llm-toolkit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-payloadsB | Fetch payloads from a JSON file with optional filters (category, context, riskLevel) |
| generate-payloadB | Generate payload variants with mutations (case, whitespace, comment, encoding, tokenBreaker, unicode) |
| bypass-wafC | Generate WAF-specific bypass variants for a payload (cloudflare, modsecurity, aws-waf, generic) |
| analyze-payloadB | Analyze a payload to detect attack type and suggest bypass strategies |
| encodeC | Encode data using various methods (url, doubleUrl, hex, base64, htmlEntity, unicode) |
| decodeC | Decode data using various methods (url, hex, base64, htmlEntity, unicode, jwt) |
| jwt-encodeC | Encode a JWT token with payload, optional secret and algorithm |
| fetch-referenceB | Fetch content from a URL reference (article, video, pdf, tweet) |
| validate-referenceC | Validate that a content reference URL is reachable |
| connect-mcpB | Connect to another MCP server via stdio transport |
| call-mcp-toolC | Call a tool on a connected MCP server |
| list-mcp-toolsB | List tools available on a connected MCP server |
| disconnect-mcpC | Disconnect from an MCP server |
| list-connected-serversA | List all connected MCP servers |
| list-categoriesA | Returns all available payload categories |
| healthB | Returns server health status |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool has a distinct purpose without overlap. analyze-payload and generate-payload are clearly different (analysis vs generation), and all other tools target unique actions or resources.
Most tools follow a verb-noun hyphenated pattern (analyze-payload, bypass-waf, etc.). The only outlier is 'health' which is a simple noun, but it's minor and the pattern is otherwise consistent.
16 tools is on the high side but still reasonable for a toolkit covering security analysis, encoding, MCP management, and reference fetching. Each tool serves a specific function, so the count is appropriate.
The tool set covers core functionalities for the stated domain: payload analysis, encoding, WAF bypass, MCP server management, and reference validation. Minor gaps like missing payload editing are acceptable for a toolkit.