Mithwire MCP

session_proxy_set

Create or update a proxy registry entry so browser profiles and sessions can reference it by name, accepting discrete fields or a server URL.

Instructions

Create or update a proxy registry entry. values accepts either discrete fields ({scheme, host, port, username, password, rotation_url, tags}) or a single server URL ({server: 'http://user:pw@host:port', rotation_url, tags}). The persisted form is always discrete fields; server is decomposed at write. Profiles and session_start reference the entry by name via the proxy_ref field.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "proxy_name": "<proxy_name>"
    },
    "name": "session_proxy_set"
  }
}

Input Schema

Name	Required	Description	Default
`merge`	No
`values`	No
`proxy_name`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 18, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a real behavioral trait — that the persisted form is always discrete fields and that a 'server' URL is decomposed at write — which is valuable non-obvious context. But it is silent on permissions/auth needs, what happens to omitted fields, and the semantics of the 'merge' flag, leaving meaningful gaps for an upsert.

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?

Three dense sentences, front-loaded with the action before the input-shape detail, and no filler. It is information-rich but the second sentence's inline field list makes it slightly heavy to parse; still efficient overall.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the description covers the dual input forms, the persisted representation, and the cross-tool referencing model well. The remaining gap is the merge/update-vs-overwrite behavior, which is central to an upsert tool and left unaddressed.

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 0%, so the description must compensate, and it does well for the complex 'values' parameter by enumerating both accepted shapes and their fields. However, it adds nothing about 'merge' (default true, undocumented) and only gestures at 'proxy_name' by saying entries are referenced by name. Partial compensation, not full.

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?

States a specific verb pair and resource ('Create or update a proxy registry entry'), which cleanly separates it from session_proxy_list, session_proxy_get, and session_proxy_delete. It also names the two accepted input shapes, so the agent knows exactly what kind of write this is before opening the schema.

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

Usage Guidelines3/5

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

The description implies usage by explaining that profiles and session_start reference entries via proxy_ref, which gives context for why one would create an entry. However, it never states when to use this versus session_rotate_proxy or session_set_fingerprint, nor any exclusions or prerequisites. Usage is implied rather than declared.

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

Deploy Server