Skip to main content
Glama
Sign In
DevFlow MCP Server

DevFlow MCP Server

by FaerberK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agent_session_create

Start an agent session to track AI work for a specific flow, returning a session ID for subsequent logging and completion calls.

Instructions

Create a new agent session for a flow. An agent session tracks a unit of work performed by the AI agent. Use this at the start of a work session to log what you're doing.

Returns the created session with its ID for subsequent log and complete calls.

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_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoType of session (e.g., "planning", "implementing", "reviewing"). Optional.
flowIdYesThe flow ID this session belongs to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.35.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool creates a session and returns its ID, but does not mention side effects, permissions, or error conditions. For a creation tool, this is adequate but not comprehensive.

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 three concise sentences: purpose, concept explanation, and usage guidance with return info. Every sentence adds value without redundancy.

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 simplicity of the tool (2 params, no output schema), the description covers the purpose, usage context, and return value. It explains the lifecycle (start, log, complete) sufficiently for an agent.

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%, so the schema already describes both parameters (flowId required, type optional). The description adds context about the session tracking purpose but no additional parameter detail beyond the schema.

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 explicitly states 'Create a new agent session for a flow', which is a specific verb+resource combination. It clearly differentiates from sibling tools like agent_session_complete and agent_session_log by focusing on creation.

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 advises using this tool 'at the start of a work session to log what you're doing', providing direct when-to-use guidance. It also mentions subsequent calls (log, complete), implying when not to use it (e.g., after work is done).

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