Skip to main content
Glama
Sign In
webshare-mcp

webshare-mcp

by jimmyallinai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

webshare_delete_ip_authorization

Deletes an IP whitelist entry from a Webshare account after confirmation, removing a previously authorized IP. Pass auth_id and confirm=true to prevent accidental deletion.

Instructions

删除一条 IP 白名单。必须传 confirm=true。

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": {
      "auth_id": "<auth_id>"
    },
    "name": "webshare_delete_ip_authorization"
  }
}

Input Schema

NameRequiredDescriptionDefault
auth_idYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 does disclose the confirm safety gate, but for a destructive delete it omits irreversibility, whether the entry can be re-added, and what permission level is required — the most important behavioral facts for an agent.

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

Conciseness5/5

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

Two short sentences with zero filler, and the destructive action plus its mandatory guard are both front-loaded.

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?

A destructive, no-annotation, no-output-schema tool with an entirely undocumented required parameter. The description should at minimum state that auth_id comes from webshare_list_ip_authorizations and that the deletion is permanent.

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. It usefully clarifies that confirm must be true despite the schema defaulting it to false — a non-obvious constraint that prevents a failed call — but auth_id is never explained, nor where to obtain it.

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 and resource (delete an IP whitelist entry), which cleanly separates it from the sibling list/add tools. It does not name those siblings explicitly, so an agent must infer the pairing rather than being routed to it.

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 gives one hard usage constraint (confirm=true is mandatory), which is real operational guidance. It says nothing about when to prefer this over webshare_add_ip_authorization or webshare_list_ip_authorizations, nor about preconditions such as the auth_id having to exist.

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