Skip to main content
Glama

generator_account

Read-onlyIdempotent

Checks remaining credits and access for paid image, voice and script services before use, and can open the Higgsfield sign-in page when requested.

Instructions

Read-only check of the paid services Dinoctor can use and what's left: Higgsfield (pictures: signed in, credits, any job running), ElevenLabs (voices: connected, plan, characters left) and whether Claude Code is here (for writing scripts). Call it before paid tools to see if they will work. sign_in: true opens the person's browser to sign in to Higgsfield themselves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generator_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
sign_inNotrue: open the person's browser at the Higgsfield sign-in page. Only when they asked to sign in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / sign_in / description
      Added value: +"true: open the person's browser at the Higgsfield sign-in page. Only when they asked to sign in."
  2. 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 readOnly/destructive/idempotent, so the description's job is to add context, and it does: it discloses the browser-opening side effect of sign_in: true and that the person completes sign-in themselves. It stops short of describing permissions, failure modes, or rate limits, but the safety profile and user-visible side effect are both covered.

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 check is stated first and each service is listed compactly; nothing is padding. The nested parentheticals make it slightly dense and run-on, costing a bit of scannability.

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?

There is no output schema, so the description carries the burden of saying what comes back, and it largely does by listing credits, characters left, plan and connection status per service. It could say more about the shape of a partial failure (e.g., one service unconfigured) but is adequate for this tool's complexity.

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?

With a single parameter at 100% schema coverage the schema already carries the definition, so a baseline 3 would be defensible. The description adds genuine nuance beyond the schema by clarifying that the sign-in is performed by the person in their own browser rather than programmatically.

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 names a specific verb and resource ('read-only check of the paid services Dinoctor can use') and enumerates exactly what is inspected per service: Higgsfield sign-in state, credits and running jobs; ElevenLabs connection, plan and characters left; Claude Code presence. That level of detail makes it clearly distinguishable from the generation siblings such as generate_picture or generate_character.

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 an explicit usage rule — 'Call it before paid tools to see if they will work' — which tells the agent exactly when to reach for it, and the sign_in parameter carries a when-not constraint ('Only when they asked to sign in'). No alternative tool is named, but the preflight framing is sufficient for correct selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.