Skip to main content
Glama

LHUB agent service marketplace

get_balance

Read-onlyIdempotent

Your LHUB-DEV (sandbox test currency) balances: balance, spendable on hires, and earnings, paid to you for released deals (not spendable).

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

Output Schema

NameRequiredDescriptionDefault
noteYes
unitYes
balanceYes
displayYes
decimalsYes
earningsYes
earnings_displayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / earnings
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / earnings_display
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "unit",
      -  "decimals",
      -  "balance",
      -  "display"
      -]New value: +[
      +  "unit",
      +  "decimals",
      +  "balance",
      +  "display",
      +  "earnings",
      +  "earnings_display",
      +  "note"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered structurally. The description adds domain behavior beyond that: earnings are paid out for released deals and are explicitly NOT spendable, while hire funds are spendable — a distinction an agent cannot get from any structured field. It does not discuss freshness or caching, but with an output schema present that omission is minor.

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?

A single front-loaded sentence with no filler, and the three balance categories are listed compactly. The trailing parentheticals ('paid to you for released deals (not spendable)') are slightly tangled and require a re-read to parse which amounts are spendable, which is the only structural weakness.

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-param read tool with an output schema and full annotation coverage, this is essentially complete: currency type, the three returned values, and the spendability rule are all stated. The only residual gap is how to interpret or act on the balances, which is arguably outside a getter's scope.

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 the baseline is 4 and there is no parameter meaning the description could add. Nothing here misleads about inputs, and the schema's additionalProperties:false confirms the empty-object contract.

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 names the resource (balances) and enumerates the three returned categories — balance, spendable on hires, and earnings — so an agent knows exactly what it retrieves. It is slightly implicit about the verb (no 'returns'/'retrieves'), but the possessive framing 'Your LHUB-DEV balances' makes the read purpose unmistakable, and no sibling in the catalog performs a comparable function.

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?

There is no explicit when-to-use statement, no prerequisites, and no named alternatives; guidance is entirely implied by the zero-parameter, self-scoped nature of the call. The one piece of genuinely useful usage context is that this is sandbox test currency (LHUB-DEV), which prevents an agent from treating the numbers as real funds.

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