Skip to main content
Glama
This connector has been deprecated

Replaced by echopai-mcp.

Duplicate listing; superseded by io.github.echopai/echopai-mcp (official MCP Registry entry).

usage

This key's credit usage for the current month: used, base_cap, base_remaining, pack_remaining (purchased top-ups, spent only after the base allowance runs out), total_remaining, plus a 6-month history in monthly. Use it to decide whether a wide sweep is affordable before starting one, and to tell a 429 that means 'out of credits' apart from one that means 'too fast' — the first will not clear by waiting. ⚠️ Consumer keys only (kind=user): partner and agent tokens are billed per contract and get 403 here — whoami reports quota for those instead. Checking usage is itself free and never cached.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does substantial work: consumer-keys-only restriction, 403 for partner/agent tokens, the fact that checking usage is free and never cached, and the semantics of a 429. It omits any statement about response shape beyond field names or about failure modes other than 403/429, so it stops just short of complete.

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 definition is front-loaded with what is returned, then usage guidance, then the consumer-key caveat, so an agent gets the essentials first. It is dense rather than padded — the parenthetical gloss on pack_remaining and the 429 explanation earn their place, though the opening enumeration is long enough that skimming costs a little.

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, but the description enumerates the returned fields and their meanings, including the ordering rule that pack_remaining is spent only after the base allowance. Combined with the key-type restriction and the 429 interpretation guidance, an agent has everything needed to call this safely and read the result.

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 description coverage is 100% and all six parameters are shared envelope controls (_jq, _spill, _fields, _intent, _max_bytes, _max_bytes_mode), each already documented in the schema. The description adds nothing about how any parameter behaves, so the schema does all the work and baseline 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 opening sentence states a specific subject and scope — this key's credit usage for the current month — and enumerates the exact fields returned (used, base_cap, base_remaining, pack_remaining, total_remaining, monthly), which compensates for the vague tool name. It further distinguishes itself from the sibling whoami by assigning quota reporting for partner/agent tokens to that tool.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance — check affordability before a wide sweep, and disambiguate a 429 'out of credits' from a 429 'too fast' — and adds an explicit exclusion with an alternative: partner/agent tokens get 403 here, use whoami instead. Both the positive case and the hand-off are named.

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