Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Credit balance

hermoso_credits
Read-only

Check account credit balance, recent priced calls, and total credits spent. Learn what costs credits: only AI model runs and Ad Spy research; publishing, scheduling, and management are free.

Instructions

Return the account credit balance, the credits this account has spent on the calls listed, those recent priced calls, 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). Check before kicking off paid generation; answer "does posting cost credits?" with NO.

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": {
-    "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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context beyond those annotations: the rule for what consumes credits, the free operations list, and the single per-call exception. This helps the agent reason about cost implications without contradicting the read-only annotation.

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 primary return value and then delivers the cost rule and usage guidance. It is somewhat longer than necessary, especially with the all-caps 'THE RULE' emphasis, but every sentence adds useful information for the agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only balance tool without an output schema, the description covers the essential return elements and the cost model well. It does not detail the exact structure of 'recent priced calls' or specify how recent, but the tool is simple enough that an agent can call it correctly with this information.

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 has zero parameters and the schema confirms this with 100% coverage. There are no parameter semantics to document, so the baseline of 4 applies. The description indirectly supports invocation by clarifying what the returned data means.

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 ('Return') and identifies the resource and the exact data returned: account credit balance, credits spent on listed calls, recent priced calls, and costModel. This clearly differentiates it from related sibling tools like buy_credits and billing_status by stating what this particular tool provides.

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 explicit guidance on when to use the tool: 'Check before kicking off paid generation.' It also preempts a common agent question by stating that posting does not cost credits. It does not explicitly name alternative tools or when not to use it, but the usage context is strong.

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