Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Set auto-reload

set_auto_reload
Idempotent

Enable or disable automatic credit reloads so the card on file is charged for a top-up pack when balance drops below a threshold. Admin-only; members are directed to ask an admin.

Instructions

Turn automatic credit reloads on or off (admin only): when the balance drops below a threshold, the card on file is charged for a top-up pack — SERVER-SIDE, even with no app open. Requires a saved card, added once in the app at first checkout/top-up; if there's none the tool tells you exactly where to add it. After that one-time card setup, agents can manage auto-reload, top-ups and plan links fully. Members (read-only billing) get an 'ask an admin' message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledYestrue to turn auto-reload on, false to turn it off
reloadCreditsNohow many credits to add each reload — must match a credit pack size (see buy_credits)
thresholdCreditsNoreload when the balance drops below this many credits

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": {
-    "applied": {
-      "description": "whether the auto-reload config was applied",
-      "type": "boolean"
-    },
-    "capUsd": {
-      "description": "monthly auto-reload spend cap in USD, if set"
-    },
-    "enabled": {
-      "description": "the resulting auto-reload state",
-      "type": "boolean"
-    },
-    "guidance": {
-      "description": "instructions when the change must be made in the app",
-      "type": "string"
-    },
-    "needsCard": {
-      "description": "true when there is no saved card yet (add one in the app first)",
-      "type": "boolean"
-    },
-    "reloadCredits": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "credits added per reload"
-    },
-    "reloadPack": {
-      "description": "the pack charged on each reload"
-    },
-    "status": {
-      "description": "auto-reload status detail",
-      "type": "string"
-    },
-    "thresholdCredits": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "reload triggers below this balance"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.15
  3. Removedv0.1.0
  4. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds substantial behavioral detail: the action is SERVER-SIDE and executes even with no app open, charges the card on file, requires a saved card, and gives specific guidance when no card exists. This goes far beyond structured annotation fields and matches the idempotentHint.

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 longer than average but every sentence carries meaningful information: purpose, permission, server-side behavior, card requirement, and member handling. It is front-loaded with the core action and does not contain filler or repetition.

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?

For a configuration tool with 3 params, no output schema, and no nested objects, the description is complete: it details prerequisites, permissions, execution behavior, and even what the tool tells the user when a card is missing. An agent has enough context to invoke it correctly and know what to expect.

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?

Schema covers all three parameters with descriptions, including 'must match a credit pack size (see buy_credits)' and 'reload when the balance drops below this many credits'. The description reinforces the parameter semantics by explaining the threshold-to-charge behavior and top-up pack concept, adding value beyond the schema alone.

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 states a specific verb and resource: 'Turn automatic credit reloads on or off' with '(admin only)' scope. It clearly distinguishes this from billing-related siblings by focusing on the auto-reload mechanism, and is not a tautology of the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when the tool applies: requires admin role, requires a saved card, and after card setup agents can manage auto-reload. It explains members will receive an 'ask an admin' message, implying a when-not-to-use condition, though it doesn't explicitly name alternative tools like buy_credits for manual top-ups.

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