Skip to main content
Glama
mako10k

Web Proxy MCP Server

by mako10k

proxy_update_target

Modify domain settings in the web proxy server to adjust monitoring parameters like header capture, body capture, and enable/disable status.

Instructions

Update target domain configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to update
descriptionNoNew description
enabledNoEnable/disable target
captureHeadersNoEnable/disable header capture
captureBodyNoEnable/disable body capture

Implementation Reference

  • Tool handler for proxy_update_target: prepares updates from args and calls targetManager.updateTarget, returns success message.
    case 'proxy_update_target':
      const updates = {};
      if ('enabled' in args) updates.enabled = args.enabled;
      if ('description' in args) updates.description = args.description;
      if ('captureHeaders' in args) updates.captureHeaders = args.captureHeaders;
      if ('captureBody' in args) updates.captureBody = args.captureBody;
      
      const updated = this.targetManager.updateTarget(args.domain, updates);
      return {
        content: [{
          type: "text",
          text: `Target updated: ${args.domain}\nStatus: ${updated ? 'success' : 'not found'}\nUpdates: ${JSON.stringify(updates, null, 2)}`
        }]
      };
  • Input schema definition for proxy_update_target tool including properties and required fields.
    proxy_update_target: {
      name: "proxy_update_target",
      description: "Update target domain configuration",
      inputSchema: {
        type: "object",
        properties: {
          domain: {
            type: "string",
            description: "Domain to update"
          },
          description: {
            type: "string",
            description: "New description"
          },
          enabled: {
            type: "boolean",
            description: "Enable/disable target"
          },
          captureHeaders: {
            type: "boolean",
            description: "Enable/disable header capture"
          },
          captureBody: {
            type: "boolean",
            description: "Enable/disable body capture"
          }
        },
        required: ["domain"]
      }
    },
  • Core updateTarget method in TargetManager class that applies configuration updates to the target domain and regenerates PAC file.
    updateTarget(domain, updates) {
      const target = this.targets.get(domain.toLowerCase());
      if (!target) {
        return false;
      }
    
      // Apply updates
      if ('enabled' in updates) target.enabled = updates.enabled;
      if ('description' in updates) target.description = updates.description;
      if ('includeSubdomains' in updates) target.includeSubdomains = updates.includeSubdomains;
      if ('captureHeaders' in updates) target.captureHeaders = updates.captureHeaders;
      if ('captureBody' in updates) target.captureBody = updates.captureBody;
      
      target.lastModified = new Date();
      this._updatePacFile();
      
      return true;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Update' implies a mutation operation, but it doesn't disclose behavioral traits like whether changes are reversible, permission requirements, rate limits, or what happens if the domain doesn't exist. It mentions 'configuration' but lacks details on scope or impact.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero waste—'Update target domain configuration' is front-loaded and appropriately sized for the tool's purpose. Every word earns its place without redundancy.

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

Completeness2/5

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

Given no annotations, no output schema, and a mutation tool with 5 parameters, the description is incomplete. It doesn't explain what 'target domain configuration' includes beyond the implied parameters, lacks error handling or success indicators, and fails to address behavioral aspects like side effects or prerequisites.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents all 5 parameters. The description adds no additional meaning beyond implying these parameters relate to 'target domain configuration', which aligns with the schema but doesn't provide extra context like default values or inter-parameter dependencies.

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

Purpose4/5

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

The description 'Update target domain configuration' clearly states the action (update) and resource (target domain configuration). It distinguishes from siblings like 'proxy_add_target' (adds new) and 'proxy_remove_target' (removes), but doesn't explicitly mention what 'target domain configuration' entails beyond the implied domain settings.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'proxy_add_target' or 'proxy_remove_target'. The description implies it modifies existing configurations but doesn't specify prerequisites (e.g., target must exist) or use cases (e.g., enabling/disabling, updating descriptions).

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/mako10k/mcp-web-proxy'

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