Skip to main content
Glama

面灵AI 面试助手

redeem_credits

Destructive

把账户中的积分兑换为面试时长与模拟面试次数:每 200 积分换 60 分钟时长与 2 次模拟面试,一次兑换全部积分,不足 200 的余数随之清零。积分余额见 get_account。会消耗用户的时长、次数或产生付款,执行前向用户说明扣费内容并取得同意。(需要用户授权,范围 account:write)

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": "redeem_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, yet the description still adds substantial non-redundant behavior: a single redemption consumes the entire balance, any remainder under 200 is forfeited, the operation may trigger a payment, and it requires the account:write authorization scope. That is exactly the extra context an agent needs before invoking a destructive, irreversible action.

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

Conciseness4/5

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

The conversion rule and the remainder-forfeiture warning are front-loaded and earn their place, and the consent requirement is stated compactly. The sentence is dense and packs several ideas into one paragraph, but nothing is redundant with the annotations.

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?

For a zero-parameter destructive tool with no output schema, the description covers the pricing rule, the irreversibility, the auth scope, and the consent gate. The only gap is what the call returns or how it fails when the balance is below the 200-point threshold, which is minor given there is no output schema to describe.

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 description appropriately spends no words on parameter syntax and instead explains the implicit 'parameter' that matters — the amount, which is always the full balance.

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?

States a specific verb and resource ('把账户中的积分兑换为面试时长与模拟面试次数') and goes further by giving the exact conversion rate (200 points → 60 minutes + 2 mock interviews) and the all-or-nothing scope. It also explicitly names the sibling for the balance check ('积分余额见 get_account'), so an agent can tell the two apart without opening any schema.

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?

It routes the pre-check to get_account and imposes a clear precondition: explain the deduction and obtain user consent before executing. What is missing is an explicit statement of when NOT to redeem (e.g. below the 200-point threshold the redemption would zero out the remainder), but the usage context is otherwise unambiguous.

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