Skip to main content
Glama
Sign In
autoflow-mcp

autoflow-mcp

Official
by inov8ing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

autoflow_open_flow

Opens Google Flow in your active browser tab, enabling immediate access to AI generation models via the Autoflow extension.

Instructions

Instruct the Autoflow extension to open Google Flow (https://flow.google.com/) in an active browser tab.

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": "autoflow_open_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosure. It adequately describes the core behavior: instructing the Autoflow extension to open a specific URL in the active browser tab. While it does not mention side effects like navigation history or page load failure, the described action is simple and low-risk.

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

Conciseness5/5

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

The description is a single, information-dense sentence. It states the action, the target resource, the exact URL, and the browsing context without any filler or redundant wording.

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?

Given the tool has zero parameters, no output schema, and no annotations, the description is fully sufficient for an agent to invoke it correctly. There are no remaining behavioral or contextual details needed for successful execution.

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, so there is no parameter ambiguity to resolve. Per the baseline for 0-parameter tools, the description needs to explain no schema fields, and it does not introduce any confusion. The lack of parameter detail is not a gap here.

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 clearly states a specific verb ('open'), a specific resource ('Google Flow'), and includes the exact URL. It also disambiguates the navigation context ('in an active browser tab'), making it distinct from sibling tools like reload_tab or clear_queue.

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?

The description gives clear context for when to use the tool: when the user wants Google Flow opened in the active browser tab. It does not explicitly name alternatives or exclusion cases, but the intended use case is unambiguous enough for an agent to select it appropriately.

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

Deploy Server

Other Tools