Skip to main content
Glama

面灵AI 面试助手

get_account

Read-only

查看当前账号:剩余面试 / 笔试时长、会员等级与到期时间、模拟面试与押题次数、网申额度,以及最近 10 笔订单的付款状态。用户通过购买链接付款后,用它确认是否到账。(需要用户授权,范围 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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so safety behavior is covered by structured data. The description contributes genuine extra context: it requires user authorization with the account:read scope, and it bounds the order history to the most recent 10 records. It still says nothing about pagination, latency, or what happens when the user has no orders, so the added value is moderate rather than rich.

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?

Three sentences, each doing work: the field inventory, the payment-confirmation trigger, and the authorization scope. The field enumeration is dense but front-loaded and skimmable. Minor cost is that the list of account fields is long and could be tightened, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description has to carry the return contents itself, and it does so by naming every field group the caller will receive, including the 10-order window. Combined with the read-only annotations and the stated auth scope, an agent has everything needed to decide and call correctly.

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 tool takes zero parameters, so there is no parameter meaning for the description to add, which puts it at the baseline. The schema is empty and fully described by construction, and the description correctly signals an argument-free call. Nothing here is wrong; there is simply nothing to elaborate.

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 gives a specific verb+resource ('查看当前账号') and then enumerates exactly what that covers: remaining interview/written-exam time, membership tier and expiry, mock-interview and question-prediction counts, application quota, and the last 10 orders' payment status. That is enough for an agent to know this is the aggregate account snapshot rather than a single-purpose getter. It does not explicitly differentiate itself from overlapping siblings such as get_auto_apply_quota or get_upgrade_offer, which keeps it short of a 5.

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 supplies a concrete usage trigger: after the user pays through the purchase link, call this to confirm whether the payment arrived. That is a real when-to-use rule an agent would otherwise have to guess. It stops short of a 5 because there is no when-not guidance and no mention of which sibling to prefer for the narrower quota or membership questions.

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