AgentShield MCP Inspector Lite
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 |
|---|---|
| analyze_toolsB | Basic Lite-edition inspection of MCP tool names, descriptions and JSON Schemas without executing target tools. |
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 1 tool
Only one tool exists, so there is zero risk of an agent confusing it with another. The tool's purpose is clearly defined.
The single tool uses a clear verb_noun pattern ('analyze_tools'), and with only one name there is no inconsistency to evaluate.
A single tool is at the lower boundary of acceptable scope. It may be intentional for a 'Lite' edition, but the set feels very thin.
The tool covers the core inspection task (names, descriptions, schemas) without execution, but lacks any auxiliary operations like listing, comparing, or exporting results—though these may be outside the Lite scope.