3ilm-mcp
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 |
|---|---|
| search_vulnerabilitiesD | – |
| get_pattern_detailsD | – |
| list_patternsD | – |
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 3 tools
The tools appear distinct: search_vulnerabilities focuses on finding vulnerabilities, list_patterns enumerates patterns, and get_pattern_details retrieves specifics for a single pattern. Minor ambiguity exists as 'patterns' could relate to vulnerabilities, but the action verbs (search/list/get) clarify intent.
All names follow the snake_case verb_noun pattern: search_vulnerabilities, get_pattern_details, list_patterns. The verb (search/get/list) and noun (vulnerabilities/pattern) placement is consistent and predictable.
Three tools is within the well-scoped range (3-15) and fits a focused read-only knowledge base for vulnerabilities and patterns. Each tool serves a distinct purpose without unnecessary redundancy.
The set covers search, list, and get-details operations, which covers typical read-only workflows. A minor gap is the lack of a dedicated 'get_vulnerability_details' tool, but search_vulnerabilities may return sufficient details to compensate.