Skip to main content
Glama
Sign In
webshare-mcp

webshare-mcp

by jimmyallinai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

webshare_subscription

Check the current Webshare subscription to view billing cycle, auto-renew status, remaining credits, and whether it is paused or rate-limited.

Instructions

查看当前订阅：计费周期、是否自动续费、剩余额度积分、是否暂停或限速。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/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. The verb '查看' (view) signals a read-only, non-mutating operation, which is the key safety fact, but the description does not state whether authentication is required, whether results are cached, or whether the call is rate-limited.

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?

A single sentence with the action front-loaded and the returned fields listed after the colon. No filler, no repetition of the tool name.

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

Completeness4/5

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

There is no output schema, so the description must convey what comes back — and it does, enumerating the four data points (billing cycle, auto-renewal, remaining credits, paused/limited status). For a zero-parameter read tool this is close to complete; only a note on the response shape or refresh semantics is missing.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The input schema is empty with 100% coverage, and there is nothing about parameters that the description could or should add.

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 gives a specific verb ('查看' / view) plus the resource (current subscription) and enumerates exactly what is returned: billing cycle, auto-renewal status, remaining quota credits, and paused/rate-limited state. It differentiates from most siblings by naming 'current subscription', though it does not explicitly contrast with the nearby webshare_plan tool.

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 word '当前' (current) implies this is the tool for inspecting the live subscription state rather than plan options, so usage is inferable. However, there is no explicit when-to-use guidance, no statement of when to prefer webshare_plan or webshare_cancel_auto_renewal instead, and no prerequisites mentioned.

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