Skip to main content
Glama

SafeSellAI

get_balance

查询 S算力余额和套餐。适用场景:深度使用前先确认余额。匿名试用暂未开放(匿名额度请查 guest_info)。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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. It does add real behavioral context: the operation is a read-style query and anonymous trial is not yet open, implying authentication is required. It says nothing about return shape, caching, rate limits, or whether the balance is per-user or per-workspace, leaving meaningful gaps for a zero-annotation tool.

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?

Three short sentences, front-loaded with the purpose and followed by the use case and the anonymity caveat. Every sentence carries information; the only mild redundancy is restating the anon limitation alongside the pointer to guest_info.

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 with no output schema, the definition covers purpose, when to call, and the important constraint that anonymous access is unavailable, with a redirect to guest_info. Since there is no output schema, the description could have sketched what the balance/package response contains, which is the one 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 no parameter meaning to add; the baseline for a parameterless schema is 4. The description correctly implies the result is scoped to the caller's own account rather than something selectable via input.

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 states a specific verb and resource in '查询 S算力余额和套餐' (query S compute-power balance and package), which is enough for an agent to tell it apart from sibling check tools like check_batch or check_image. It does not explicitly name those siblings, but the anonymity clause routes one adjacent case to guest_info, so the boundary is mostly clear.

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 an explicit when-to-use condition: check the balance before heavy usage. The parenthetical '匿名额度请查 guest_info' adds a when-not/alternative pointer for the anonymous-quota case. What is missing is guidance on calling frequency or whether to re-check after consumption.

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