Skip to main content
Glama
Sign In
webshare-mcp

webshare-mcp

by jimmyallinai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

webshare_proxy_config

View proxy configuration details, including country and ASN assignments, replaceable countries, and ASN/IP range pools, with credential fields masked by default.

Instructions

查看代理配置：国家与 ASN 分配、可替换的国家、ASN 与 IP 段池。默认打码凭证字段。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "webshare_proxy_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_credentialsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose one genuinely useful behavioral trait — credential fields are masked by default, a sensitive-data handling rule the schema does not express — but says nothing about permissions, whether the read is side-effect free, or what the response looks like.

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?

Two short clauses, front-loaded with the verb and resource, then the returned content, then the masking default. No filler, though the enumeration of return contents is slightly list-like rather than prioritized.

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?

For a simple one-parameter read with no output schema, the description usefully previews the returned sections (country/ASN allocation, replaceable countries, pools) and flags credential masking. It still leaves the sibling boundary and the security implications of include_credentials 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?

The single parameter has 0% schema description coverage, so the description must compensate. '默认打码凭证字段' implicitly explains that include_credentials controls unmasking, which is meaningful, but it never states the parameter's name, its boolean semantics, or what un-masking exposes.

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 (查看) plus the resource (代理配置) and enumerates what the config view covers: country/ASN allocation, replaceable countries, ASN and IP-range pools. That is enough to separate it from webshare_list_proxies or webshare_profile, though it never names a 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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives among the 13 sibling tools. The only implicit hint is the credential-masking default, which suggests an opt-in path, but the agent must infer when this tool beats webshare_list_proxies.

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