# RevCent MCP Guide: `EditProject`

AI/MCP-focused guide for editing a RevCent Project.

---

## Related Documentation

Read `Project Overview` first. It explains how Projects function as durable pseudo repositories for AI/MCP context.

| Guide | Link | Why It Matters |
|---|---|---|
| Project Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewProject.md` | Explains Projects as durable AI/MCP pseudo repositories for businesses, objectives, reporting workspaces, external-agent source-of-truth context, and operational notes. |
| GetProjects | `https://revcent.com/documentation/markdown/mcp/operation/GetProjects.md` | Find possible existing Projects before deciding which Project to edit. |
| GetProject | `https://revcent.com/documentation/markdown/mcp/operation/GetProject.md` | Retrieve the Project's current name, description, and associated entities before editing. |
| ProjectAssociateEntity | `https://revcent.com/documentation/markdown/mcp/operation/ProjectAssociateEntity.md` | Use when the issue is missing entity association, not Project metadata. |
| ProjectDisassociateEntity | `https://revcent.com/documentation/markdown/mcp/operation/ProjectDisassociateEntity.md` | Use when an entity should be removed from Project context without deleting the entity. |
| GetProjectNotes | `https://revcent.com/documentation/markdown/mcp/operation/GetProjectNotes.md` | Retrieve Project Note titles and metadata when Project history is needed before editing. |
| GetProjectNote | `https://revcent.com/documentation/markdown/mcp/operation/GetProjectNote.md` | Retrieve the full content of a specific Project Note when needed. |
| CreateProjectNote | `https://revcent.com/documentation/markdown/mcp/operation/CreateProjectNote.md` | Briefly record why Project metadata was changed when the edit has future context value. |
| SearchProjectNotes | `https://revcent.com/documentation/markdown/mcp/operation/SearchProjectNotes.md` | Search Project Notes by keyword or phrase, optionally within a specific Project, when note content or history needs to be found quickly. |

---

## Operation Summary

Operation:

```text
EditProject
```

Purpose:

```text
Edit a specific Project using the Project ID.
```

Use `EditProject` to update a Project's `name` and/or `description`.

A Project is a durable RevCent context container that behaves like a **pseudo repository** for AI/MCP work. Editing a Project changes the repository label and/or README-like source-of-truth description.

Important schema behavior:

```text
Only provide the fields that should be edited.
```

Do not use `EditProject` to associate or disassociate entities. Use `ProjectAssociateEntity` or `ProjectDisassociateEntity` for entity membership changes.

---

## When to Use

Use `EditProject` when:

- the Project name is vague or misleading,
- the Project description does not explain the current purpose,
- the Project scope has changed,
- the Project should clarify whether it is for a business, objective, report, workflow, agent, or notes repository,
- the Project should better serve as a source of truth for AI/MCP or an external agent,
- the Project's README-like description needs new warnings, boundaries, assumptions, or operating rules,
- the current Project metadata causes AI/MCP to retrieve or use the wrong context.

Do not edit a Project only because a related entity changed. If the Project name/description still accurately represent the pseudo repository, create or update notes and associations instead.

---

## Input Schema

| Field | Type | Required | Description |
|---|---:|---:|---|
| `project_id` | string | Yes | 20-character Project ID. |
| `name` | string | No | New Project name. Use only when the Project label should change. |
| `description` | string | No | New Project description. Use only when the README-like Project purpose, scope, boundaries, or operating context should change. |

Schema behavior:

```text
project_id is required.
name and description are optional.
Only include fields that should be edited.
```

---

## Editing Guidance

Before editing, determine what problem the edit is solving:

| Problem | Correct Action |
|---|---|
| Name is vague or misleading | Edit `name`. |
| Description does not explain purpose/scope | Edit `description`. |
| Project now represents a different objective or agent purpose | Edit `name` and/or `description`, then briefly note the reason. |
| Entity is missing from Project context | Use `ProjectAssociateEntity`, not `EditProject`. |
| Entity is wrongly attached to the Project | Use `ProjectDisassociateEntity`, not `EditProject`. |
| Historical detail needs to be preserved | Use Project Notes, not the Project description, unless it changes the current source-of-truth scope. |

Project descriptions should summarize the current source of truth. They should not become long history logs. Use Project Notes for history.

---

## Naming Guidance

Project names may be:

- business-specific,
- objective-specific,
- reporting-specific,
- agent-specific,
- workflow-specific,
- notes/context-specific.

Good naming patterns:

```text
[Business Name] [Implementation / Migration / Setup]
[Objective] Initiative
[Metric / Report] Review
[Agent Purpose] Source of Truth
[Workflow] Operating Notes
```

Avoid vague names:

```text
Setup
Changes
Stuff
New Project
Notes
Main
```

When editing a business-specific Project, keep the business name unless the original Project was incorrectly named. When editing an objective/report/agent Project, keep the objective/report/agent purpose clear.

---

## Description Guidance

The Project description is the Project's README-like source-of-truth statement.

Edit the description when AI/MCP needs a better understanding of:

- why the Project exists,
- whether it is for a business, objective, report, workflow, agent, or notes repository,
- current scope and boundaries,
- relevant RevCent entity categories,
- systems involved,
- warnings, assumptions, or confirmation requirements,
- what future AI/MCP should review before acting.

Keep the description focused on the current Project purpose. Do not turn it into a full change log.

---

## Example Request Bodies

Edit only the description:

```json
{
  "project_id": "XXXXXXXXXXXXXXXXXXXX",
  "description": "Pseudo repository for the renewal recovery agent, including allowed actions, escalation requirements, related RevCent entities, safety constraints, and current operating context."
}
```

Edit the name and description:

```json
{
  "project_id": "XXXXXXXXXXXXXXXXXXXX",
  "name": "Gateway Approval Rate Monitoring",
  "description": "Reporting workspace for gateway approval-rate analysis, including reviewed date ranges, relevant payment entities, findings, assumptions, and follow-up recommendations."
}
```

---

## Output Schema

Successful output can include:

| Field | Description |
|---|---|
| `api_call_id` | 20-character API call ID. |
| `api_call_unix` | Unix timestamp when the API call was initiated. |
| `code` | API response code. `1` indicates success. |
| `project_id` | 20-character Project ID. |
| `result` | Result message. |

---

## Recommended Workflow

```text
1. Use GetProject to inspect the current name, description, and associated entities.
2. If history matters, use GetProjectNotes and GetProjectNote to review only relevant Project Note content.
3. Decide whether the issue is Project metadata, entity association, or historical context.
4. If Project metadata should change, run EditProject with only the fields that should change.
5. Briefly create a Project Note when the metadata change has future context value.
6. Use GetProject again to verify the updated Project metadata.
```

Project Notes are mentioned here only as a companion memory mechanism. For details about note title/content behavior and retrieval, use:

```text
https://revcent.com/documentation/markdown/mcp/operation/OverviewProject.md
https://revcent.com/documentation/markdown/mcp/operation/CreateProjectNote.md
https://revcent.com/documentation/markdown/mcp/operation/GetProjectNotes.md
https://revcent.com/documentation/markdown/mcp/operation/GetProjectNote.md
```

---

## Common Mistakes to Avoid

Do not:

- overwrite the Project description with vague content,
- rename a Project so broadly that future AI loses scoped context,
- treat Projects as only business containers,
- remove the business name from a business-specific Project unless correcting the scope,
- obscure the objective/report/agent purpose in a non-business Project,
- send unchanged fields unless intentionally editing them,
- use `EditProject` for entity association or disassociation,
- put a full change log into the Project description,
- edit Project metadata without checking the current Project first when context is important.

---

## Final AI/MCP Instruction

Use `EditProject` for targeted Project `name` and/or `description` updates. Treat the Project name as the pseudo repository label and the Project description as the README-like source of truth. Always provide `project_id`, only include fields that should change, keep the Project purpose clear, and briefly record important metadata changes with Project Notes when future AI/MCP will benefit from that context.


---
Document Parent Directory
* [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.