Skip to main content
Glama

洋葱财报OnionData-MCP

查询额度

get_usage
Read-onlyIdempotent

查询本账号额度(quota / usage):当前档位 free / VIP / SVIP、日调用护栏与积分余额的上限、已用、剩余与重置时间,以及最近到期的积分包。本工具不计积分,积分耗尽后仍可用。

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_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dateYes
tierYes
credit_packsNo
credits_freeYes
credits_paidYes
token_prefixNo
credits_totalYes
subscribe_hintNo
daily_call_usedYes
daily_call_limitYes
daily_call_reset_atNo
daily_call_remainingYes
max_credits_per_callNo
credits_nearest_expiry_atNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the call is free of credit cost and still works when the balance is depleted — exactly the kind of fact an agent needs before deciding to call it.

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 content is front-loaded: the resource and returned fields come first, followed by the credit-cost caveat. The enumeration is dense but each item (tier, guardrail, balance, reset time, expiring packs) is substantive; only the parenthetical 'quota / usage' gloss is mildly redundant.

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 an output schema present, the description need not restate return values, yet it summarizes them helpfully, and it covers the one behavioral fact (no credit consumption) that the schema and annotations cannot express. Nothing an agent needs in order to call this zero-parameter tool is missing.

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; the baseline for a no-parameter tool applies. The description correctly implies no input is required.

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 names a specific verb (查询) and resource (本账号额度/quota/usage), then enumerates exactly what is returned: tier (free/VIP/SVIP), daily call guardrail, credit balance upper bound/used/remaining/reset time, and recently expiring credit packs. An agent can tell precisely what this tool yields without opening the output 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 gives clear context for when to call it (checking account quota/credits) and adds a useful condition: the tool does not consume credits and remains usable after credits are exhausted. It does not name alternatives or exclusions, but the sibling set (dimensions, company records, indicators) is unrelated, so no routing guidance is needed.

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