Skip to main content
Glama
Sign In
DevFlow MCP Server

DevFlow MCP Server

by FaerberK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agent_session_list

Review past work sessions by listing all agent sessions for a flow, including status, timing, and summary.

Instructions

List agent sessions for a flow. Returns all sessions with their status, timing, and summary. Use this to review past work sessions on a flow.

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": {
      "flowId": "<flowId>"
    },
    "name": "agent_session_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowIdYesThe flow ID to list sessions for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.35.0

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description carries full burden. It states returns include status, timing, and summary, which adds value. However, it does not disclose pagination, sorting, rate limits, or potential side effects, which are common for list operations.

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?

Two sentences, each adding value: first states action, second clarifies output and usage. No redundant information.

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

Completeness4/5

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

Given simple input schema and no output schema, the description provides key output fields and usage context. It lacks error handling info, but for a listing tool, it is sufficiently complete.

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 description coverage is 100% for the single parameter flowId, providing its purpose. The tool description does not add extra detail beyond that, meeting the baseline of 3.

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 the tool lists agent sessions for a flow, which is a specific verb-resource pair. It distinguishes from siblings like agent_session_create or agent_session_log by focusing on listing all sessions.

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?

It explicitly says 'Use this to review past work sessions on a flow,' providing clear context. No alternatives or when-not-to-use are mentioned, but the usage is unambiguous given sibling tools.

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