Skip to main content
Glama
Sign In
webshare-mcp

webshare-mcp

by jimmyallinai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

webshare_profile

Fetches Webshare account profile details—ID, email, name, and email verification status—to confirm account identity and verification state.

Instructions

查看 Webshare 账号资料（id、邮箱、姓名、邮箱验证状态）。

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

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 burden. '查看' implies a read-only operation and the tool takes zero parameters, so side effects are effectively impossible, but the description never explicitly states read-only behavior, authentication requirements, or error conditions.

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 short sentence with the resource front-loaded and the returned fields in a parenthetical. Every element earns its place and there is no filler.

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?

With no output schema, the description usefully compensates by listing the exact fields returned (id, email, name, verification status). For a zero-parameter read tool this is nearly complete; only auth/error behavior is left unstated, which is minor here.

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 has zero parameters, which is the baseline-4 case. Nothing about parameter meaning needs explanation, and the description correctly implies no input is required.

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 ('查看' / view) and resource ('Webshare 账号资料'), and enumerates the returned fields (id, email, name, email verification status). It is clearly distinguishable from siblings like webshare_subscription or webshare_plan by resource, though it never explicitly contrasts itself with them.

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?

Usage is only implied by the verb 'view' — an agent can infer this is the tool to call when it needs account identity data. There is no explicit statement of when to prefer it over webshare_subscription/webshare_plan, nor any prerequisite or exclusion noted.

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