Skip to main content
Glama
Sign In
Hermoso

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Credit balance

hermoso_credits
Read-onlyIdempotent

Check credit balance, recent priced calls, and the cost model before paid AI generation or Ad Spy research; publishing, scheduling, and ads management are free.

Instructions

Return the credit balance, recent priced calls with their credits, and costModel (the one-sentence rule of what costs credits). THE RULE: only AI model runs and Ad Spy research spend credits; publishing, scheduling, ads management, analytics, comments, DMs and connectors are FREE on every plan (X is the single per-call exception; xCost gives its exact credits per post, with and without a link). Check before kicking off paid generation; answer "does posting cost credits?" with NO. Paid plans: media models at cost + 10% (memberRate).

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": {
-    "accountBalance": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "the account’s Hermoso credit balance (authoritative when authed)"
-    },
-    "balance": {
-      "description": "raw vendor meter balance (operator/local-dev surface)",
-      "type": "number"
-    },
-    "recentCalls": {
-      "description": "recent priced calls with their credit deltas",
-      "items": {},
-      "type": "array"
-    },
-    "sessionStart": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "vendor balance at session start (operator surface)"
-    },
-    "sessionUsed": {
-      "description": "credits used this session",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.15
  3. Removedv0.1.0
  4. First observedv0.1.0

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, so the safety profile is covered. The description adds genuinely non-obvious behavior: which actions spend credits, that X posting is the sole per-call exception with xCost, and the memberRate markup on paid plans.

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 core purpose is front-loaded in the first sentence, but the middle 'THE RULE' sentence packs in a lot of capitalized asides (X exception, xCost, link pricing) that read as stacked caveats rather than tight prose. It is dense but nearly all of it is load-bearing.

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?

No output schema exists, so the description compensates by naming the three returned components (balance, recent priced calls, costModel). For a zero-parameter read tool with full annotation coverage, an agent has everything needed to call it correctly.

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 the baseline of 4 applies and there is nothing the description could add on parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a specific verb and resource set: credit balance, recent priced calls with their credits, and the costModel rule. That is far more concrete than 'get credits', though it never explicitly contrasts itself with siblings like billing_status or buy_credits, so an agent must infer the boundary.

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?

It gives concrete usage instructions: 'Check before kicking off paid generation' and 'answer "does posting cost credits?" with NO'. Those are real when-to-use signals, but there is no explicit when-not or named alternative tool for balance/payment actions.

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