Inspect the active Google Flow workspace to return prompt inputs, action buttons, and canvas nodes, enabling AI assistants to understand and automate page interactions.
Inspects active Google Flow workspace: returns prompt inputs, action buttons, and canvas nodes.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the content of the response (prompt inputs, action buttons, canvas nodes), which implies a non-mutating inspection, but it never states that it is read-only, requires an active browser/tab, or has any side effects or failure modes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with a colon-delimited list of returned artifacts; no filler. It is as short as it can be while still naming the resource and output.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description is the only source of truth, and it only sketches the returned fields rather than their structure or how they map to the canvas. For a no-param inspection tool this is adequate but leaves real gaps about prerequisites and result shape.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the schema has nothing to explain and the baseline of 4 applies. The description correctly adds no parameter detail because none exists.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (inspects) and resource (active Google Flow workspace) and even enumerates what it returns. It is clear on its own, but it never distinguishes itself from the closest sibling flow_status, which likely also reports workspace state.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use or when-not-to-use guidance and no mention of alternatives among the seven flow_* siblings. An agent must infer that this is the read/inspect step versus flow_click, flow_screenshot, or flow_status.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.