Skip to main content
Glama
Sign In
Mithwire MCP

Mithwire MCP

by elendil-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

session_proxy_get

Retrieve a single proxy registry entry by proxy name to review its configuration for browser session setup or proxy management.

Instructions

Get one 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_get"
  }
}

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.8/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 behavioral burden. It implies a read-only lookup but does not state whether it is safe, what permissions are needed, or how it behaves when the proxy name is not found.

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 single sentence is efficiently front-loaded and contains no filler. It is appropriately short for a simple getter, though the extreme brevity contributes to gaps documented in other dimensions.

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

Completeness3/5

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

An output schema exists, so the return value does not need explanation in the description. The tool is simple with one required parameter, but the absence of annotations, parameter detail, and any usage or error context leaves it only minimally complete.

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%, so the description must compensate for the undocumented proxy_name parameter. Saying 'by name' adds only minimal selector context, with no format, constraints, or examples for the expected proxy name value.

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 states a specific verb ('Get') and resource ('proxy registry entry') with a scoping condition ('by name'). This clearly distinguishes it from sibling write/delete/list tools like session_proxy_list, session_proxy_set, and session_proxy_delete, though it does not name any sibling explicitly.

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 when-to-use guidance is provided. It does not state prerequisites, when to prefer this over session_proxy_list, or what happens if the named entry is absent. Usage can only be inferred from the tool name.

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