MCP Server For Local
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 |
|---|---|
| proxy_tool_callC | 代理工具，根据工具名动态调用其他服务端的工具，输入格式为字典：{'tool': 'tool_name', 'args': {...}} |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clearly defined and distinct purpose as a proxy for dynamic tool calls.
There is only one tool name, so naming consistency is inherently perfect. The tool follows a clear snake_case pattern (proxy_tool_call), which is appropriate for its function.
A single tool is generally too few for most server purposes, as it limits functionality and forces all operations through a proxy. This feels thin and may not provide a complete or intuitive interface for agents.
The server's purpose is unclear from the single tool, but as a proxy server, it lacks any direct operations or domain coverage. There are significant gaps, as it relies entirely on external tools without providing its own functionality, making it severely incomplete for any defined domain.