Skip to main content
Glama
Sign In
Hermoso

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Billing status

billing_status
Read-onlyIdempotent

View your account's plan, credit balance, auto-reload status, card on file, and admin rights before changing billing settings. Read-only and free.

Instructions

Show this account's billing at a glance: current plan (quote plan.priceUsd per plan.period), credit balance, whether auto-reload is on, whether a card is on file, and whether YOU (this key) have ADMIN rights to change billing. Read-only, free. Call it before upgrade_plan / set_auto_reload to know what's possible — members have read-only billing. IN A SHARED TEAM WORKSPACE A MEMBER SEES THE PLAN AND THE BALANCE ONLY: the workspace owner's payment card and auto-reload belong to them and are not reported (billingScope:'member'). Never tell a member there is no card on file — the honest answer is that you cannot see it. plan.memberRate: media models at cost + 10%; plan.legacy: an older plan kept at its price.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "autoReload": {
-      "description": "auto-reload config ({enabled, thresholdCredits, reloadCredits, available})"
-    },
-    "balanceCredits": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "the current credit balance"
-    },
-    "card": {
-      "description": "the saved card ({brand, last4}) when present"
-    },
-    "isAdmin": {
-      "description": "whether this key can change billing",
-      "type": "boolean"
-    },
-    "paymentMethodOnFile": {
-      "description": "whether a card is saved for one-click charges",
-      "type": "boolean"
-    },
-    "plan": {
-      "description": "the current plan ({id, label, monthlyUsd})"
-    },
-    "role": {
-      "description": "this key’s billing role (admin/member)",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changedv0.1.15
    • addedOutput schema / properties / balanceCredits / anyOf
      Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / balanceCredits / type
      Removed value: -"number"
  3. Addedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/destructive, but the description goes well beyond them: it declares the call is free, explains the shared-workspace scope edge case (billingScope:'member' hides owner card/auto-reload), and even instructs how to phrase the absence of card data honestly. This is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with the core purpose before the caveats, and every sentence carries non-redundant information. It is on the long side with several ALL-CAPS passages that read as shouting, which slightly hurts scannability but not comprehension.

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?

With no output schema, the description must explain what comes back, and it does so thoroughly, including the tricky member-vs-owner case that would otherwise cause an agent to hallucinate missing payment data. Nothing an agent needs to call or interpret this tool is missing.

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?

There are zero input parameters, so the baseline is 4. The description instead documents the meaningful output fields (plan.priceUsd, plan.period, billingScope, plan.memberRate, plan.legacy), which adds real interpretive value even though no input semantics are needed.

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 names a specific resource and enumerates exactly what is returned: plan (with priceUsd/period), credit balance, auto-reload state, card-on-file, and caller admin rights. An agent can distinguish this from upgrade_plan, set_auto_reload, and buy_credits purely from the text.

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?

It states explicit when-to-use ('Call it before upgrade_plan / set_auto_reload to know what's possible') and an explicit precondition/limitation ('members have read-only billing'). The alternative tools are named, so routing is unambiguous.

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

Deploy Server

Other Tools