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. To add an **Antigravity** Google account from inside this chat, use
`add_antigravity_start` -> open the URL -> paste the `code` back with
`add_antigravity_submit(code, state)`. `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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), and the description adds substantial context beyond them: it spends nothing, it returns a single most-blocking next_step with text/text_en/url/command, and it explains that sign-in steps occur in the user's own browser. This is rich behavioral disclosure that an agent needs to act correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core guidance is front-loaded and clear, but the description sprawls across several paragraphs and drifts into tangential territory (the 'support' Telegram paragraph, and detailed Antigravity routing instructions) that is not essential to selecting or invoking this tool.

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 return-value burden and does so: it names the important next_step field, its subfields, and the weekly limit. It also tells the agent what to do with the result, so nothing needed to call and use this tool is missing.

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 there is nothing for the description to clarify and the baseline of 4 applies. The description instead documents the returned fields, which is a different concern handled under contextual completeness.

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 preflight-check purpose: 'What this key still needs before it can do everything', plus a one-shot enumeration of what it reports (Google account, free trial, GitHub link, weekly limit). It implicitly distinguishes itself from siblings by naming add_account_token as the fallback and add_antigravity_start/submit as the alternate path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger conditions: '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 also names the concrete alternatives and when to prefer each (run the command, add_account_token only as fallback, add_antigravity_* for Antigravity accounts).

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