Skip to main content
Glama

KA-Forge

quota

查这个密钥今天还剩多少次、多少字。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses very little. It does not state that this is a read-only/non-consuming operation, whether calling it itself consumes quota, whether 'today' means a fixed reset boundary or a rolling window, or what the response shape is. For a zero-argument tool the risk is low, but the behavioral profile is essentially inferred from the verb 查 rather than stated.

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?

One short sentence with no filler and the quantity being measured front-loaded ('how many times, how many characters'). It is efficiently sized, though the terseness leaves no room for the usage or behavioral context noted above.

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

Completeness3/5

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

With no output schema and no annotations, the description must carry both behavioral and return-value semantics. It does convey what is returned at a high level (remaining count and remaining characters), which is a real contribution, but it omits the reset/timezone semantics of 'today' and whether the numbers are remaining or consumed. Adequate for a trivial read tool, not complete.

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 no per-parameter meaning to add; the schema is trivially complete and the empty object matches the description's implicit 'for this key' scoping. Baseline 4 applies since nothing is missing that a parameter description could supply.

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 (查/check 'how much is left') and a specific resource: the remaining daily allowance for 'this key,' expressed in both call count and character count. That is concrete enough to distinguish it from the only sibling, rewrite, which does content transformation rather than quota introspection. It loses a point only because it never explicitly contrasts itself with any alternative.

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?

There is no explicit when-to-use statement, no prerequisite, and no exclusion. Usage is only implied by the phrasing 'today is left,' which suggests pre-flight checks before consuming quota, but the agent must infer that itself. Nothing tells the agent what to do if the quota is exhausted.

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