hvip MCP Server

xlayer_unsubscribe

Cancel a subscription by providing its subscription ID. Remove subscriptions you no longer need from your account.

Instructions

[L:READ] CAT:[链上] | → 请先调用 agent_catalog

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": {
      "subscriptionId": "<subscriptionId>"
    },
    "name": "xlayer_unsubscribe"
  }
}

Input Schema

Name	Required	Description	Default
`subscriptionId`	Yes	要取消的订阅ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Jul 30, 2026

TDQS

C2.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 must disclose behavioral traits. Despite being an 'unsubscribe' operation (likely destructive), the description includes '[L:READ]' which misleadingly suggests a read-only operation. There is no mention of side effects, authorization requirements, or confirmation of success.

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

Conciseness2/5

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

The description is extremely brief but sacrifices clarity for conciseness. It uses non-standard tags and a Chinese sentence that does not efficiently convey the tool's purpose or usage. Every part should add value, but here it is cryptic.

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 tool with one required parameter and no output schema, the description should explain prerequisites (e.g., getting a subscriptionId from xlayer_list_subscriptions) and the effect of unsubscribing. It only mentions calling agent_catalog without connecting the dots, leaving the agent under-informed.

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 input schema fully documents the sole parameter 'subscriptionId' with a Chinese description meaning 'subscription ID to cancel'. With 100% schema coverage, the baseline is 3. The description adds no additional parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is cryptic and does not explicitly state that the tool is for unsubscribing from a subscription. It includes non-standard tags like '[L:READ]' and 'CAT:[链上]' which do not clarify the purpose. The instruction '请先调用 agent_catalog' suggests a prerequisite but does not define the tool's primary function.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., xlayer_list_subscriptions to view subscriptions, xlayer_subscribe to create one). The only hint is a prerequisite to call agent_catalog, but no context on when unsubscribing is appropriate or what preconditions exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server