Skip to main content
Glama
Sign In
Mithwire MCP

Mithwire MCP

by elendil-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

session_proxy_delete

Delete a proxy registry entry by name to remove unused or outdated proxy configurations from the browser automation session.

Instructions

Delete a proxy registry entry by name.

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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
proxy_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about permanence, whether deletion fails or is a no-op for unknown names, or what happens to live sessions using that proxy. 'Delete' implies destruction but no consequences are disclosed.

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?

A single front-loaded sentence with zero filler, though its brevity is partly under-specification rather than disciplined editing.

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?

This is a destructive mutation with no annotations and no output guidance needed (output schema exists), but the description omits the behavioral context an agent needs to call it safely: what is removed, what breaks, and how an unknown name is handled.

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

Parameters2/5

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

Schema description coverage is 0% and the only parameter, proxy_name, is documented solely by its title. 'By name' merely restates the parameter name; it adds no format, case-sensitivity, or lookup-failure semantics to compensate for the coverage gap.

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?

States a specific verb (delete) and resource (a proxy registry entry) plus the selector (by name), which cleanly separates it from session_proxy_set/get/list siblings. It only lacks an explicit contrast naming the siblings it replaces.

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?

There is no guidance on when to delete versus when to use session_proxy_set or session_rotate_proxy, and no note about preconditions or effect on sessions currently bound to the proxy. The agent must infer usage entirely from the verb.

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

Deploy Server

Other Tools