Skip to main content
Glama

upstream_servers

Destructive

Add, remove, update, and list upstream MCP servers. Automatically quarantine new servers to block Tool Poisoning Attacks.

Instructions

Manage upstream MCP servers - add, remove, update, and list servers. Includes Docker isolation configuration and connection status monitoring. SECURITY: Newly added servers are automatically quarantined to prevent Tool Poisoning Attacks (TPAs). Use 'quarantine_security' tool to review and manage quarantined servers. NOTE: Unquarantining servers is only available through manual config editing or system tray UI for security.

Docker Isolation: Use 'isolation_json' parameter to configure per-server Docker images, CPU/memory limits, and network isolation. Example: {"enabled": true, "image": "node:20", "network_mode": "bridge"}.

SMART PATCHING (update/patch): Uses deep merge - only specify fields you want to change. Omitted fields are PRESERVED, not removed. Examples:

  • Enable server: {"operation": "patch", "name": "my-server", "enabled": true} - only enabled changes

  • Enable isolation: {"operation": "patch", "name": "my-server", "isolation_json": "{"enabled": true}"} - enables isolation with defaults

  • Update image: {"operation": "patch", "name": "my-server", "isolation_json": "{"image": "python:3.12"}"} - other isolation fields preserved

  • Add env var: env_json merges with existing vars

  • Replace args: args_json replaces entirely (arrays not merged)

  • Remove field: use 'null' (e.g., isolation_json: "null" removes isolation)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
args_jsonNoCommand arguments for stdio servers as a JSON array of strings (e.g., '["mcp-server-sqlite", "--db-path", "/path/to/db"]'). For update/patch: REPLACES all existing args (arrays are not merged).
commandNoCommand to run for stdio servers (e.g., 'uvx', 'python')
enabledNoWhether server should be enabled (default: true)
env_jsonNoEnvironment variables for stdio servers as JSON object (e.g., '{"API_KEY": "value"}'). For update/patch: MERGES with existing vars (new keys added, existing keys updated).
headers_jsonNoHTTP headers for authentication as JSON object (e.g., '{"Authorization": "Bearer token"}'). For update/patch: MERGES with existing headers (new keys added, existing keys updated).
isolation_jsonNoDocker isolation config as JSON object. MERGES with existing settings - only provided fields change. Use 'null' to remove isolation entirely. Example: '{"image": "python:3.12"}' updates only the image.
linesNoNumber of lines to tail from server log (default: 50, max: 500) - used with tail_log operation
nameNoServer name (required for add/remove/update/patch/tail_log operations)
oauth_jsonNoOAuth config as JSON object. MERGES with existing settings. Use 'null' to remove OAuth entirely. Fields: client_id, client_secret, scopes (array - replaces).
operationYesOperation: list, add, remove, update, patch, tail_log. 'update' and 'patch' use smart merge - only specified fields change, others preserved. For quarantine operations, use the 'quarantine_security' tool.
protocolNoTransport protocol: stdio, http, sse, streamable-http, auto (default: auto-detect)
urlNoServer URL for HTTP/SSE servers (e.g., 'http://localhost:3001')
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description comprehensively discloses behavioral traits beyond annotations: auto-quarantine for new servers, unquarantine limitations, smart merge behavior for update/patch operations, and non-merge replacement for arrays. No contradiction with annotations (destructiveHint: true).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but well-structured with clear sections (security, Docker isolation, smart patching examples). Every sentence serves a purpose, though it could be slightly more concise without losing important detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (12 parameters, multiple operations, security and Docker features), the description is remarkably complete. It covers operations, security, merge behavior, and parameter usage with examples. No output schema, but return values are obvious.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description adds significant value through concrete examples (e.g., Docker isolation, env vars, smart patching) and clarifies merge vs replace semantics beyond the schema's simple descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Manage upstream MCP servers - add, remove, update, and list servers' with specific verbs and resource. It distinguishes from sibling tools like quarantine_security by explicitly directing quarantine operations to that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit guidance on when to use this tool versus alternatives (e.g., 'For quarantine operations, use the quarantine_security tool'). It also details smart patching behavior and security precautions, leaving little ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smart-mcp-proxy/mcpproxy-go'

If you have feedback or need assistance with the MCP directory API, please join our Discord server