Skip to main content
Glama
jstibal

Openterms-mcp

by jstibal
OverviewSchemaRelated ServersScoreDiscussions
Python

check_balance

Check USDC balance in minor units for workspace spending verification. Enables monitoring of available funds against policy caps.

Instructions

Check workspace USDC balance (minor units, 1 USDC = 1,000,000).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • openterms_mcp_server.py:247-254 (handler)
    The implementation of the 'check_balance' tool handler in handle_tool function.
    elif name == "check_balance":
    resp = client.get("/v1/ledger", headers=_headers())
    if resp.status_code == 200:
        data = resp.json()
        entries = data.get("entries", [])
        balance = sum(e["amount"] for e in entries) if entries else 0
        return f"Balance: {balance:,} USDC minor units (${balance / 1_000_000:.2f} USDC)"
    return _format_error(resp)
  • openterms_mcp_server.py:59-62 (schema)
    The tool definition (schema) for 'check_balance'.
        "name": "check_balance",
    "description": "Check workspace USDC balance (minor units, 1 USDC = 1,000,000).",
    "inputSchema": {"type": "object", "properties": {}},
},

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It successfully discloses the unit format ('minor units, 1 USDC = 1,000,000') which is critical for interpreting return values. However, missing auth requirements, rate limits, error conditions, or cache behavior that would help an agent handle failures or retries.

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?

Single sentence with zero waste. Front-loaded with action and resource, followed immediately by essential unit semantics. Every clause earns its place.

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?

Appropriate for a simple read operation with zero parameters. While no output schema exists, the description clarifies the return value format through unit specification. Could be improved by explicitly stating it returns an integer/balance amount, but sufficient for tool selection.

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 present (empty schema), triggering the baseline score of 4 per evaluation rules. Description correctly omits parameter discussion since none exist.

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 provides specific verb ('Check') + specific resource ('workspace USDC balance'). Clearly distinguishes from siblings which focus on policies, receipts, and provider activity rather than financial balance queries. The parenthetical unit clarification further specifies the resource format.

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?

No explicit when-to-use or when-not-to-use guidance provided. No alternatives mentioned. However, the financial nature of the operation (balance checking) creates implicit context distinguishing it from receipt verification or policy management siblings.

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/jstibal/openterms-mcp'

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