Skip to main content
Glama
joinwell52-AI

fcop-mcp

by joinwell52-AI
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

init_solo

Initialize a solo FCoP project: generates canonical directories, configuration, documentation, and protocol rules for single-agent coordination.

Instructions

Initialize an FCoP project in Solo mode (one AI, no dispatch).

Solo mode is for projects where a single agent works directly with ADMIN. Rule 0.b still applies: the agent uses files to split itself into proposer and reviewer, even though there is no second role.

Since 3.0.2 fresh init produces the v3 topology (per spec §1.1): fcop/_lifecycle/{inbox,active,review,done,archive}/ plus retained reports/ / issues/ / shared/. Superseded v2 buckets (tasks/, log/) are no longer created on fresh init.

Beyond fcop.json and the canonical directories, this also deposits fcop/LETTER-TO-ADMIN.md (the user manual), creates the workspace/ cage with a starter README (per Rule 7.5), deploys the bundled solo three-layer docs (TEAM-README / TEAM-ROLES / TEAM-OPERATING-RULES + roles/ME.md, both zh and en) to docs/agents/shared/, and (per ADR-0006) drops the bundled protocol rules into .cursor/rules/*.mdc + AGENTS.md + CLAUDE.md. Existing copies are archived under .fcop/migrations/<timestamp>/ before being overwritten.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_codeNoThe single role code (uppercase letters / digits / underscore, must start with a letter; ``ADMIN`` and ``SYSTEM`` are reserved). Default: ``ME``.ME
role_labelNoDisplay label (e.g. ``"我自己"``). Currently recorded in ``extra`` for future use; the library does not yet consume it. Safe to omit.
langNoOutput language, ``zh`` or ``en``.zh
forceNoWhen ``True``, overwrite an already-initialized project. All previous artifacts (config, letter, workspace README, ``shared/`` docs, protocol rule files) are archived under ``.fcop/migrations/<timestamp>/`` before the new content lands. Use this when ADMIN wants to switch from team mode back to solo, or re-init solo with a different ``role_code``. Default: ``False``.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden. It details file creation, archiving on force, and version differences. It lacks mention of idempotency or error conditions when already initialized, but overall is transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose, but is somewhat lengthy with detailed bullet points. Every sentence adds value, but could be more concise without losing information.

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 complexity (4 optional params, output schema exists), the description covers directory structure, file generation, archiving behavior, and version differences comprehensively. It leaves no obvious gaps.

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 baseline is 3. The description adds minimal extra context (e.g., role_label is for future use). It does not significantly enhance understanding 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 clearly states that the tool initializes an FCoP project in Solo mode, distinguishing it from init_project. It specifies the resource (FCoP project) and the mode, providing a unique identity.

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 explains Solo mode as one AI without dispatch, implying its use case. However, it does not explicitly contrast with init_project or specify when not to use it, leaving some ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/joinwell52-AI/FCoP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server