Skip to main content
Glama
Sign In
DeepSeek MCP Server

DeepSeek MCP Server

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_user_balance

Read-onlyIdempotent

Retrieve the current DeepSeek account balance and availability status for account health checks and diagnosing provider-side failures.

Instructions

Return the current DeepSeek account balance and availability status. This tool takes no parameters and is read-only. Use it for account health checks when diagnosing provider-side failures.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusNo
messageNo
retryableNo
error_typeNo
suggestionNo
is_availableNo
balance_infosNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "balance_infos": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "currency": {
+            "type": "string"
+          },
+          "granted_balance": {
+            "type": "string"
+          },
+          "topped_up_balance": {
+            "type": "string"
+          },
+          "total_balance": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "currency",
+          "total_balance",
+          "granted_balance",
+          "topped_up_balance"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error_type": {
+      "enum": [
+        "deepseek_api_error",
+        "tool_execution_error"
+      ],
+      "type": "string"
+    },
+    "is_available": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "status": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "suggestion": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Addedv0.5.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the description's 'read-only' clause is redundant with structured data. The genuinely additive content is the mention of an 'availability status' return and the diagnostic framing, which is useful but modest given the rich annotations.

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?

Two front-loaded sentences with no padding; purpose comes first and the usage hint second. The 'takes no parameters and is read-only' clause slightly duplicates schema/annotation data, keeping it just short of perfect.

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?

With an output schema present, a parameterless input, and full annotation coverage, the description only needs to convey purpose and when to reach for it — both are stated. Nothing an agent needs to invoke it correctly 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?

Zero parameters, so the baseline is 4. The description correctly states 'takes no parameters,' which matches the empty schema and prevents an agent from guessing at inputs.

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?

States a specific verb and resource ('Return the current DeepSeek account balance and availability status'), which no sibling tool covers — siblings are chat/completion/file operations. An agent can immediately tell this is an account-diagnostic read.

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?

Gives a clear selection condition: 'Use it for account health checks when diagnosing provider-side failures.' It does not name explicit exclusions, but no sibling overlaps semantically, so the routing guidance is sufficient.

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

Deploy Server

Other Tools