mcp-lens
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_capabilitiesA | Search the capability catalog by keyword or natural language. Always call this first. Capability keys are not guessable and are not listed anywhere else — this is the only way to discover them. Returns short summaries; call get_capability_schema() on a result before calling execute_capability(). |
| get_capability_schemaA | Get the input schema for a capability key returned by search_capabilities(). |
| execute_capabilityA | Execute a capability by key, with input matching its schema. |
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
Each tool has a distinct role in a clear pipeline: search to discover, get schema to understand inputs, and execute to run. There is no overlap or ambiguity between the three tools.
All tool names follow a consistent verb_noun pattern: search_capabilities, get_capability_schema, execute_capability. The naming clearly communicates the action and target for each tool.
Three tools is perfectly scoped for a capability catalog interface. Each tool is necessary for the workflow, and there are no redundant or extraneous tools.
The tool set covers the full intended workflow: discovering capabilities, understanding their schemas, and executing them. There are no obvious gaps in the core purpose of the server.