Skip to main content
Glama
Sign In
webshare-mcp

webshare-mcp

by jimmyallinai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

webshare_add_ip_authorization

Adds an IP address to a Webshare account's whitelist to authorize that address for proxy use.

Instructions

新增一条 IP 白名单。

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": {
      "ip_address": "<ip_address>"
    },
    "name": "webshare_add_ip_authorization"
  }
}

Input Schema

NameRequiredDescriptionDefault
ip_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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. It states only that an entry is added and says nothing about behavior beyond that: duplicate handling, whether it takes effect immediately, permission requirements, or side effects are all left silent for a mutation tool.

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

Conciseness3/5

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

The definition is a single front-loaded sentence with no waste, but that brevity comes at the cost of under-specification rather than genuine efficiency. It does not add value over the name.

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?

For a mutation tool with no annotations and no output schema, the description should explain prerequisites, the result, and duplicate behavior. None of that is present, leaving an agent with too little to call it confidently.

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 description does not name or describe the single parameter. It implies an IP is involved but gives no format guidance (IPv4, CIDR, multiple addresses?), so the agent has no help beyond the schema's bare 'ip_address' string type.

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 and resource (add a new IP whitelist entry), and the sibling set (list/delete IP authorizations) makes the intended operation unambiguous. It is clear but very terse, and it never names how it differs from related tools.

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 mention of alternatives such as webshare_delete_ip_authorization or what happens if the IP already exists. The agent must infer the correct context entirely 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