fcop-mcp

Overview Schema Source Related Servers Discussions Admin

Redeploy Rules

redeploy_rules

Re-deploy bundled FCoP protocol rules to Cursor, AGENTS.md, and CLAUDE.md after a package update, eliminating version drift. Admin-only.

Instructions

ADMIN-only. Re-deploy bundled FCoP protocol rules to the project.

Writes the wheel-bundled :file:fcop-rules.mdc / :file:fcop-protocol.mdc to four locations so any agent host the project runs under sees the same rules:

.. code-block:: text

<root>/.cursor/rules/fcop-rules.mdc       # Cursor IDE
<root>/.cursor/rules/fcop-protocol.mdc    # Cursor IDE
<root>/AGENTS.md                          # Codex / Cursor / Devin / generic
<root>/CLAUDE.md                          # Claude Code CLI

Run this after pip install -U fcop-mcp (or -U fcop) to refresh on-disk copies to the newly packaged versions. fcop_report() shows when this is needed via the version drift warning.

Per ADR-0006, agents must NOT invoke this tool themselves — only ADMIN does, explicitly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Output language, ``zh`` or ``en``.	zh
`force`	No	When ``True`` (default) overwrite existing copies. ``False`` skips files that already exist (no-op for an up-to-date project).
`archive`	No	When ``True`` (default) and ``force=True``, the existing copy is moved to :file:`.fcop/migrations/<timestamp>/rules/<rel>` before being overwritten so ADMIN can diff or roll back. ``False`` skips archiving (destructive — only safe when the project has no local edits).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.4May 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations provided, the description carries the full transparency burden. It discloses that the tool writes files, overwrites existing content when force is true, archives previous versions when archiving is enabled, and can behave destructively when archiving is disabled. It also flags the ADMIN-only authorization requirement.

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 organized into a clear summary, a file-location list, a usage trigger, and an access restriction. It is slightly verbose but every sentence adds operational context that is not present in the schema.

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 that no annotations are provided, the description carries the full burden. It covers purpose, destination files, upgrade timing, drift detection, destructive behavior, and the ADMIN-only restriction, which makes the tool's context 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 coverage is high since both parameters already have detailed descriptions explaining defaults and behavior. The tool description does not add much meaning to the parameters beyond context for when the operation is appropriate, which is more about usage than parameter semantics.

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 immediately identifies the action as re-deploying bundled FCoP protocol rules to specific project files. It names the resource ('bundled FCoP protocol rules'), the destination file set, and the tool's role in refreshing on-disk copies. This leaves little ambiguity about what the tool does.

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

Usage Guidelines5/5

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

The description explicitly states when to run the tool: after `pip install -U fcop-mcp` or `fcop`, and mentions that `fcop_report()` signals when it is needed via version drift. It also gives a hard restriction that only ADMIN may invoke it, per ADR-0006, which is essential usage guidance.

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