Skip to main content
Glama

My MCP usage and spend

mycel_usage
Read-only

Show your own MCP call history: total calls, credit spend and a per-tool breakdown over the last N days. Requires an API key. |查询本 Key 最近 N 天的 MCP 调用次数、积分消费与按工具明细。需要 API Key。

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, 1-90 | 回看天数

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the auth requirement and confirms the data is scoped to the caller's own key over a bounded window, but it says nothing about the default window when days is omitted or how the breakdown is ordered.

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 English sentence is front-loaded and wastes nothing. The full Chinese restatement doubles the text for a single reader without adding new information, though the localization is a deliberate choice.

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 one-parameter read tool with no output schema and adequate annotations, the definition covers what is returned and what is required. The only meaningful gap is the default look-back window when the optional days argument is not supplied.

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 coverage is 100% and the single param already documents its 1-90 range, so the schema does the heavy lifting. The description restates 'over the last N days' but adds no behavior for the no-argument case, which is the one genuinely ambiguous aspect.

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 names a specific verb ('Show') and a precise resource ('your own MCP call history') and enumerates the payload: total calls, credit spend, and a per-tool breakdown. That resource is clearly distinct from a balance or card listing, but no sibling tool is named, so differentiation is left implicit.

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 states one prerequisite ('Requires an API key') and implies the use case of auditing your own spend, but gives no explicit when-to-use versus when-not, nor does it point to mycel_balance or any other sibling for balance-versus-history 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.