Skip to main content
Glama
Sign In
FlowState by DialectForge

FlowState by DialectForge

Official
by dialectforge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

start_here

Read-onlyIdempotent

Call first in every project conversation to return the project brief as text—rules, handoff, reviews, conflicts, todos, changes, decisions, learnings—or omit project to list projects.

Instructions

CALL THIS FIRST in every conversation about a project. Returns the brief as text: hard rules, a handoff note if any, review mode, possible conflicts, open todos (and claims) and problems, recent changes, decisions and learnings. No project: lists projects. Side effects: opens or reuses the automatic session, notes when you looked, runs the user's opt-in git capture.

Input Schema

NameRequiredDescriptionDefault
sizeNoquick, standard (default) or deep.standard
folderNoWorking folder, if no project is given.
projectNoName or id. Omit to list projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.4.3
    • changedInput schema / properties / folder / description
      Previous value: -"Working folder; picks the project if none is given."New value: +"Working folder, if no project is given."
    • changedInput schema / properties / project / description
      Previous value: -"Project name or id. Omit to get the project list."New value: +"Name or id. Omit to list projects."
    • changedInput schema / properties / size / description
      Previous value: -"quick (~1,500 chars), standard (4,000, default) or deep (12,000)."New value: +"quick, standard (default) or deep."
  2. Changed2 schema fields changedv2.3.0
    • changedInput schema / properties / folder / description
      Previous value: -"Working folder; picks the project if project is omitted."New value: +"Working folder; picks the project if none is given."
    • changedInput schema / properties / size / description
      Previous value: -"quick (~1,500 chars), standard (4,000, default) or deep (12,000, full context)."New value: +"quick (~1,500 chars), standard (4,000, default) or deep (12,000)."
  3. Changed3 schema fields changedv2.1.0
    • changedInput schema / properties / folder / description
      Previous value: -"Working folder; its name is matched to a project if project is not given"New value: +"Working folder; picks the project if project is omitted."
    • changedInput schema / properties / project / description
      Previous value: -"Project name or id"New value: +"Project name or id. Omit to get the project list."
    • changedInput schema / properties / size / description
      Previous value: -"quick (about 1,500 characters), standard (4,000) or deep (up to 12,000)"New value: +"quick (~1,500 chars), standard (4,000, default) or deep (12,000, full context)."
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses non-obvious side effects beyond the annotations: it opens or reuses the automatic session, records when the agent looked, and runs the user's opt-in git capture. These are exactly the observable effects an agent should know about before calling a nominally 'read-only' tool, and the opt-in qualifier on git capture is a useful caveat.

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?

Three dense clauses: the call-order instruction, the payload enumeration, and the side-effect disclosure. The most important directive is front-loaded in capitals, and no sentence is redundant.

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?

With no output schema, the description carries the return-value burden and does so by listing the brief's contents. Combined with the fallback behavior and side effects, an agent has everything needed to call this correctly on the first turn of a session.

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%, so the schema already documents size, folder, and project, including the 'Omit to list projects' behavior the description repeats. The description adds no meaning about the quick/standard/deep tradeoff or folder-vs-project precedence, so baseline 3 applies.

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 states a specific verb and resource ('Returns the brief as text') and enumerates the exact sections returned (hard rules, handoff note, review mode, conflicts, todos, problems, recent changes, decisions, learnings). It also names the fallback behavior ('No project: lists projects'), so an agent knows precisely what this tool produces.

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?

'CALL THIS FIRST in every conversation about a project' gives an explicit, unambiguous trigger condition, and the no-project branch is spelled out. It stops short of naming the sibling manage_* tools or stating when to use those instead, which keeps it from a 5.

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