check_balance
Get agent balance in minor units (kopecks).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
x402 Market Intelligence + Russian Web Access
by com.ruscrape
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not disclose behavioral traits like read-only, auth requirements, or side effects beyond the unit detail.
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?
Extremely concise (twelve words, one sentence) with no redundant information. Front-loaded purpose.
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?
Adequate for simple read operation but lacks output format details and error conditions. No output schema, so description should specify return structure more explicitly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has agent_id with 0% description coverage; tool description adds no meaning to the parameter, leaving agent_id entirely undefined.
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?
Description clearly states the action (get) and resource (agent balance) with specific unit (kopecks). It distinguishes from siblings like topup_balance.
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?
Implies usage for checking balance but provides no explicit when-to-use, when-not, or alternatives. No guidance compared to topup_balance.
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.
TDQS
A3.5/5.0
Disambiguation4/5
Tools are largely distinct, but fetch_ru and fetch_web overlap as the former is a specialization of the latter; descriptions clarify the difference, so agents should select correctly. Other tools (check_domain vs register_ru_domain, x402_*) have clear boundaries.
Naming Consistency4/5
Most tools follow a verb_noun snake_case pattern (check_balance, fetch_web, topup_balance), but the x402_* group uses a domain prefix rather than a verb. This is consistent within its subgroup but deviates from the overall pattern.
Tool Count5/5
12 tools cover a broad but well-scoped set of capabilities (fetching, RU-specific access, domains, code execution, balance, x402 services). Each tool has a distinct role and the count is within the ideal range.
Completeness4/5
The tool surface covers the main workflows: fetching with country/JS options, RU proxy/domain services, balance management, code execution, and x402 discovery/verification. Minor gaps like domain deletion or a generic service list are not critical for the stated purpose.