gflow-cli

Overview Schema Source Related Servers Discussions Admin

gflow_get_credits

Read the current Google Flow credit balance for one saved profile or all profiles without spending credits; set all_profiles=true to choose an account for generation.

Instructions

Read the current Google Flow credit balance for one saved profile or all profiles - the number Flow's account menu shows, read from flow.google.com in that profile's browser (one browser launch per profile, sequential for all_profiles). Spends no credits. Set all_profiles=true when choosing an account for generation; partial profile failures remain visible in the result. Set refresh=true to renew a signed-out session (rewrites that profile's saved cookies) in a headless browser and read again (slower - one more Chrome launch per signed-out profile; a revoked session still needs gflow auth login). The tier fields (sku, service_tier, user_paygate_tier, subscription_credits) are always null: flow.google.com does not report them.

Input Schema

Name	Required	Default
`profile`	No	default
`refresh`	No
`all_profiles`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.86.0Oct 22, 2026

addedInput schema / properties / refresh

Added value: +{
+  "default": false,
+  "title": "Refresh",
+  "type": "boolean"
+}

First observedSep 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: discloses no credits spent, one browser launch per profile, sequential launching for all_profiles, partial failure visibility, and the important side effect that refresh rewrites saved cookies in a headless browser (slower, revoked sessions need auth login). This is rich behavioral disclosure beyond schemas.

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?

Purpose is front-loaded in the first clause, and the dense parentheticals carry real information. It is long but nearly every clause earns its place; minor density could be trimmed.

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?

An output schema exists so return values needn't be explained, and the description covers the remaining gaps an agent would need: side effects of refresh, failure behavior, and the permanently-null tier fields explained by the source limitation.

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 coverage is 0%, so the description must compensate, and it does for refresh and all_profiles with concrete semantics and side effects. The 'profile' parameter is only implied ('one saved profile', 'that profile's browser') rather than explicitly defined, keeping it just below a 5.

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?

States a specific verb and resource ('Read the current Google Flow credit balance') and even identifies the source of truth ('flow.google.com in that profile's browser'). Clearly distinguishable from all sibling generation/auth tools.

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?

Gives explicit conditional guidance: 'Set all_profiles=true when choosing an account for generation' and 'Set refresh=true to renew a signed-out session'. It doesn't explicitly route against the nearest sibling (gflow_auth_status) for session handling, so not a 5.

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