Skip to main content
Glama

面灵AI 面试助手

get_upgrade_offer

Read-only

查看用户当前是否有升级券(购买满 2 次尝鲜包后发放的一次性折扣)、折扣多少、适用哪些商品、何时过期。下单时自动抵扣,无需填写。(需要用户授权,范围 account:read)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish a safe read-only, non-destructive, closed-world call, so the remaining burden is low. The description still adds real context beyond them: the authorization requirement and scope (account:read), the trigger condition that produces a coupon (two trial-pack purchases), and the fact that redemption is automatic — all of which shape how the agent should act on the result.

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?

One sentence front-loads the core question and then lists the sub-fields returned, followed by a short parenthetical on auto-application and the auth scope. There is no filler, and the auth caveat is placed where it can be scanned quickly.

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 has to say what comes back, and it does (existence, discount size, eligible products, expiration). Combined with the auth note, an agent has enough to decide whether to call it and how to interpret the answer; only the response shape and the behavior for a user with no coupon are left implicit.

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 there is nothing for the description to disambiguate and the baseline is 4. The schema is a closed empty object, consistent with the description giving no argument guidance.

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 uses a concrete verb+resource: it checks whether the user has an upgrade coupon, and it enumerates exactly what the answer contains (discount amount, eligible products, expiry). It does not name a sibling alternative, but the purpose is still unambiguous from the text alone.

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?

It tells the agent that the coupon is deducted automatically at checkout and that nothing needs to be filled in, which implicitly limits the stage at which this tool matters. However, it never states when to call this versus related tools such as get_product_overview or get_purchase_link, nor any preconditions, so usage is only implied.

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