Skip to main content
Glama

面灵AI 面试助手

get_purchase_link

Read-only

生成某个套餐的购买链接,交给用户在浏览器中打开:用户登录面灵AI 后自动进入该套餐的付款,支持支付宝与微信支付。商品 ID 取自 list_plans。

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": {
      "productId": "<productId>"
    },
    "name": "get_purchase_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYeslist_plans 中的商品 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare that this is a non-destructive, non-open-world read. The description adds real behavioral context: the result is a URL handed to the user, login is required, payment opens automatically, and Alipay/WeChat are supported. It omits whether the link expires, is single-use, or is bound to one account, which matters for a purchase link.

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 compact sentence that front-loads what is produced, then how it is used, then where the ID comes from. No filler or redundant restatement 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?

This is a simple one-parameter tool with no output schema, and the description compensates by explaining that the return value is a browser-openable checkout link with specific payment methods. Only link lifetime / reuse semantics are left unstated, a minor gap for a read-only link generator.

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 coverage is 100% and the single productId property already carries a description pointing at list_plans. The description repeats that provenance ('商品 ID 取自 list_plans') but adds no format, validation, or retrieval detail beyond the schema, so the baseline of 3 applies.

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

Purpose5/5

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

The description gives a specific verb+resource: it generates a purchase link for a plan (套餐的购买链接), and states the intended handoff to the user's browser. It also names the source of the required ID via 'list_plans', which connects it to a concrete sibling rather than leaving the agent to guess.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: call this to produce a checkout link the user opens themselves, after which login leads straight to payment. It does not say when NOT to use it or name an alternative path (e.g., an in-app upgrade flow), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources