Skip to main content
Glama

openFlow

by io.github.molkex
OverviewDiscussionsAdmin

flow_status

Read-onlyIdempotent

What this key still needs before it can do everything — READ-ONLY, spends nothing.

Call this BEFORE the first generation of a session, whenever a call is refused, and
whenever the user asks why something does not work. It answers in one shot: is a
Google account connected, how much of the free trial is left, is the key linked to a
GitHub identity, how much of this week's free limit is left (`weekly`).

The important field is `next_step`: it is the single most blocking thing right now,
with ready-made wording (`text` in Russian, `text_en` in English) and a `url` to open.
When it is null, nothing is missing.

DO NOT keep this to yourself. If `next_step` is set, say it to the user in their own
language and give them the URL — a step like signing in happens in THEIR browser
and cannot be done by you. When `next_step` is about connecting a Google account it
also carries `command` (personal, per OS): run it for the user in their terminal, it
submits the token by itself — no copying or pasting. add_account_token is only the
fallback. `support` is the operator's Telegram, the service's only
human channel; there is no email on file for a self-registered key, so nobody will
reach out to the user first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'READ-ONLY, spends nothing,' adding the useful credit-consumption angle. It goes further than annotations by describing the next_step contract, the personal per-OS command that self-submits a token, and the support-only Telegram channel, though some of this overlaps with return-value detail.

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?

Front-loaded with purpose and safety in the first line, and the later sentences carry genuine behavioral guidance rather than filler. It is nonetheless multi-paragraph and heavy on ALL-CAPS emphasis for a zero-parameter status call, so it is slightly more verbose than strictly necessary.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly, naming next_step, text/text_en/url, command, weekly, and support. An agent has everything needed to call it and act on the result 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; there is nothing for the description to clarify about inputs. The referenced add_account_token is a sibling tool, not a parameter, so it does not affect this dimension.

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?

States a specific capability: it reports what the key still needs before it can generate, listing the concrete checks (Google account connected, trial remaining, GitHub link, weekly limit). A specific verb+resource is present, but the description never contrasts itself with close siblings such as flow_health, flow_dashboard, or check_credits, so the agent must infer the distinction.

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 triggers — call before the first generation, when a call is refused, or when the user asks why something fails. It also names add_account_token as the fallback alternative, but does not state when this tool should NOT be used versus other status tools.

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

All openFlow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources