MCP Inspector as MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| insp_tools_listC | List all tools exposed by an MCP server. Connects, lists tools, and disconnects. |
| insp_tools_callC | Call a tool on an MCP server. Connects, calls the tool, and disconnects. |
| insp_resources_listC | List all resources exposed by an MCP server. |
| insp_resources_readC | Read a specific resource from an MCP server. |
| insp_resources_templatesB | List resource templates exposed by an MCP server. |
| insp_prompts_listC | List all prompts exposed by an MCP server. |
| insp_prompts_getC | Get a specific prompt from an MCP server. |
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 7 tools
Every tool has a clearly distinct purpose targeting different MCP server components: prompts (get/list), resources (list/read/templates), and tools (list/call). There is no overlap or ambiguity in functionality, making it easy for an agent to select the correct tool.
All tools follow a consistent 'insp_[component]_[action]' pattern with snake_case, using clear verbs like get, list, read, call, and templates. This predictability enhances usability and reduces confusion.
With 7 tools, the server is well-scoped for inspecting MCP servers, covering prompts, resources, and tools comprehensively. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides complete coverage for inspecting MCP servers, including listing and accessing prompts, resources (with templates), and tools (with calling capability). There are no obvious gaps, ensuring agents can perform all necessary inspection tasks.