Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Billing status

billing_status
Read-only

Check current billing status: plan, price, credit balance, auto-reload, card on file, and admin rights. Read-only, use before changing plans or auto-reload.

Instructions

Show this account's billing at a glance: current plan (id + label + the price it is ACTUALLY billed — quote plan.priceUsd per plan.period, not plan.monthlyUsd), 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.

Input Schema

TableJSON 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.9/5.0
Behavior5/5

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

Even though readOnlyHint is already true in annotations, the description adds substantial behavioral detail beyond annotations: how to quote the price (priceUsd per period, not monthlyUsd), the member-scoped omission of the owner's card and auto-reload settings, and the warning never to tell a member there is no card on file. This is exactly the kind of context annotations cannot express.

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?

The description is long but information-dense, with the core purpose front-loaded and every subsequent clause adding operational or safety-relevant meaning. The member-scope warning is clearly emphasized and earns its length.

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 fully enumerates what the caller can expect to learn: current plan details, credit balance, auto-reload status, card presence, own admin rights, and the member-scope variation. For a zero-parameter read-only tool, nothing essential 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?

The tool takes zero parameters and the empty input schema documents that fully, so there is no parameter burden for the description to carry. The description instead correctly uses its space to explain the result semantics and permission-scoping rules.

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 uses a specific verb ('Show this account's billing at a glance') and enumerates exactly what data is returned: plan id/label/actual price, credit balance, auto-reload state, card on file, and the key's admin rights. It clearly distinguishes this read-only status tool from mutation siblings like upgrade_plan and set_auto_reload.

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?

The description explicitly says 'Call it before upgrade_plan / set_auto_reload to know what's possible' and explains that members have read-only billing. It also gives a concrete when-not-to-infer rule: in a shared team workspace, members only see plan and balance, and must not be told the card is absent.

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