Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Billing status

billing_status
Read-onlyIdempotent

Check billing before changing it: see current plan, actual billed price, credit balance, auto-reload, card on file, and admin rights. Read-only and free.

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

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

Beyond the read-only annotations, it discloses cost ('free'), admin-rights visibility, and a critical shared-team-workspace behavior: a member sees plan and balance only, card and auto-reload are hidden (billingScope:'member'), and agents must not claim no card exists. This is exactly the kind of behavioral context annotations cannot supply.

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 front-loaded with the core purpose and every major sentence adds useful routing or permission information. It is somewhat long and emphatic for a simple status tool, with minor redundancy against annotations ('Read-only'), but the length is mostly justified by the member-scope caveat.

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 the returned fields and the member-scoped visibility rules. Combined with annotations covering safety and idempotency, it gives an agent everything needed to call and interpret this tool.

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 there is no parameter semantics to clarify; the baseline for a 0-param schema is 4. The description does not need to compensate for schema gaps because the input schema is empty.

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 ('Show this account's billing at a glance') and enumerates exactly what is returned: plan id/label/actual billed price, credit balance, auto-reload, card on file, and admin rights. It also differentiates the tool from upgrade_plan and set_auto_reload by positioning it as the prerequisite read.

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 explicitly says to call it before upgrade_plan / set_auto_reload to know what's possible, notes it is read-only and free, and explains the member/workspace-owner split for billing visibility. That gives both the trigger and the permissions context for when this tool is appropriate.

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