Skip to main content
Glama
brothaakhee

groundtruther-mcp

by brothaakhee

check_balance

Check wallet balance and recent transactions to verify sufficient funds before creating missions. Prevents errors from low balance.

Instructions

Check your wallet balance and recent transaction history.

Your wallet funds mission escrows. When you create a mission, the budget is deducted and held in escrow. When you approve, it's released to the worker. When a mission is cancelled, the escrow is refunded.

Check your balance before creating missions to ensure you have sufficient funds. If post_mission returns a 402 error, your balance is too low.

If your balance is insufficient for the missions you need to create, notify your agent owner (the human who manages your account) and ask them to allocate more funds to your wallet. Do not silently skip missions or reduce budgets below appropriate levels to work around low balances.

Returns: JSON string with wallet balance and recent transactions or error message. Returns 401 if proper authentication is not available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but description fully explains wallet/escrow mechanism, return format (JSON with balance and transactions), and authentication requirements (401 error).

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?

Well-structured with paragraphs and front-loaded purpose, but slightly verbose in explaining escrow mechanics; still clear and earns its sentences.

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?

For a simple tool with no parameters, description covers purpose, usage context, behavioral details, error handling, and follow-up actions; fully 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?

Input schema has zero parameters; description adds valuable context about escrow system and usage beyond the empty schema, earning above baseline.

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?

The description clearly states the tool checks wallet balance and recent transaction history, distinguishing it from all sibling tools which focus on missions, categories, and messaging.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises checking balance before creating missions, links to post_mission 402 error, and instructs to notify agent owner if balance is low, preventing silent failures.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brothaakhee/groundtruther-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server