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, is video paid for.

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 linking GitHub happens in THEIR browser
and cannot be done by you. `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.8/5.0
Behavior5/5

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

Beyond the annotations' readOnlyHint and idempotentHint, the description discloses important behavioral details: `next_step` is the most blocking field, null means nothing is missing, and the output includes ready-made text in Russian and English plus a URL. It also explains the human support channel and the fact that no one will proactively contact the user, adding real context beyond the annotations.

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 longer than strictly necessary but every sentence contributes value: usage timing, output interpretation, and user-facing action steps. It is front-loaded with the most important constraint ('READ-ONLY, spends nothing') and then flows logically from call timing to output meaning to required follow-through. Slightly verbose for a zero-parameter tool, but not padded.

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?

For a simple status-check tool with no parameters and no output schema, the description fully compensates: it explains what the tool returns, which field matters most (`next_step`), how to interpret null, and what the agent must do with the result. Even the human-channel nuance is covered, making the description sufficient for safe and correct invocation.

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 is an empty object, so there is no parameter semantics to clarify. Baseline 4 applies because the description wisely invests no space on parameters and instead focuses on output behavior, which is the relevant semantic content for this tool.

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 opens with 'what this key still needs before it can do everything' and immediately labels the tool as 'READ-ONLY, spends nothing,' which clearly identifies its diagnostic purpose. It then enumerates the exact questions it answers (account connected, trial remaining, GitHub linked, video paid), making the tool's role unmistakable and distinct from sibling generation tools.

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?

The description gives 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 provides post-call guidance on how to surface `next_step` to the user, leaving no ambiguity about when and how the tool should be used.

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