Skip to main content
Glama
deepseek-mcp-server

deepseek-mcp-server

DeepSeek account balance

deepseek_balance

Check remaining DeepSeek API credit for the account behind your API key, broken down by currency, to monitor available balance before making calls.

Instructions

Show the remaining credit on the DeepSeek account behind your API key, per currency.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. "Show" signals a read-only, non-mutating operation and "behind your API key" implies account scoping, but nothing is said about authentication requirements, rate limits, or whether the call fails when credit is exhausted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, and the key qualifier "per currency" is placed at the end where it sharpens rather than buries the purpose. Nothing could be removed without losing meaning.

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 zero-parameter read tool this is nearly complete: it tells the agent what is returned (remaining credit) and at what granularity (per currency). With no output schema, a brief note on the returned fields or error conditions would close the remaining gap.

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 to disambiguate; the baseline for a parameterless tool is 4. The description correctly asks for no inputs and adds that results are broken out per currency.

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?

"Show the remaining credit on the DeepSeek account" pairs a specific verb with a specific resource, and "per currency" clarifies the shape of the answer. It is clearly distinguishable from siblings like deepseek_chat or deepseek_models, though it doesn't name them explicitly.

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?

Usage is implied by the resource name: an agent would call this when it needs to know remaining credit. There is no explicit statement of when to use it, prerequisites, or any alternative route, but for a zero-parameter read tool the implied context is adequate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.