Skip to main content
Glama
Sign In

Clipia

by io.github.clipia-ai
OverviewDiscussionsAdmin

get_balance

Read-onlyIdempotent

Get the connected account credit balance and 30-day API call count plus net settled ledger spend. API keys cover their operations; OAuth covers account API/MCP operations. Reservations and refunded charges are excluded.

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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context beyond annotations: API key versus OAuth coverage for operations, and the fact that reservations and refunded charges are excluded from the reported figures. It stops short of describing output shape or pagination, but no output schema exists and the metrics are named.

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?

The description is three compact sentences and front-loads the core purpose. The auth-scope sentence is somewhat dense and slightly cryptic, but every sentence contributes relevant information about what is returned and what is excluded.

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 parameterless read-only tool with no output schema, the description is nearly complete: it names the returned metrics and explains auth coverage and exclusion rules. It could be stronger by clarifying whether the figures are scoped to a specific account or workspace, but the essential context for correct invocation is present.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly avoids inventing any.

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 states a specific verb and resource: get the connected account credit balance, plus 30-day API call count and net settled ledger spend. This is far more specific than the tool name alone and clearly distinguishes it from all generation-oriented sibling tools.

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?

Usage is implied by the purpose: check account balance, call count, and spend. However, the description does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or exclusions for calling it. With no similarly-scoped sibling, the omission is less harmful but still a gap.

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

All Clipia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources