Skip to main content
Glama
Sign In
google-flow-mcp

google-flow-mcp

by RohaanA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List agent sessions

flow_list_agent_sessions
Read-only

List agent chat sessions for a Flow project to track or resume conversations. Provide the project ID obtained from flow_list_projects.

Instructions

Flow agent chat sessions in a project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "flow_list_agent_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFlow project id (from flow_list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds nothing further: no pagination behavior, no ordering, no volume expectations for what could be a long session list. For a bare read tool this is the minimum, but no value is added beyond the annotation.

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?

It is a single short phrase with no waste, but it is not a well-formed sentence and is arguably under-specified rather than concise. Brevity here reflects missing content, not efficient packaging.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only list tool with a fully documented parameter and no output schema, the definition is technically sufficient to invoke. However, it gives no sense of what a session is or what the listing contains, which would help an agent confirm this is the right tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single project_id parameter is fully documented in the schema, including its provenance (from flow_list_projects). The description adds no parameter detail, which is acceptable here since the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun fragment ("Flow agent chat sessions in a project") that restates the tool title without stating an action verb. It does convey the resource and its project scoping, but it does not distinguish itself from the nearby flow_agent_chat sibling or otherwise clarify the operation.

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

Usage Guidelines2/5

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

There is no indication of when to call this versus alternatives such as flow_agent_chat, nor any stated preconditions. The reader must infer usage entirely from the name.

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