Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

update_control_config_note

Update existing control documentation notes using preview-then-confirm workflow. Modify markdown content and topics before saving changes to compliance audit records.

Instructions

Update an existing documentation note on a control.

✅ PURPOSE This tool updates an existing note that was previously created on a control. It allows modification of the note content, topic, or both.

✅ CONFIRMATION-BASED SAFETY FLOW

  • When confirm=False: → The tool returns a PREVIEW of the updated markdown note. → The user may edit the note before confirming.

  • When confirm=True: → The note is permanently updated and saved.

Args: controlId (str): The control ID where the note exists (required). noteId (str): The note ID to update (required). assessmentId (str): The assessment ID or asset ID that contains the control (required). notes (str): The updated documentation content in MARKDOWN format (required). topic (str, optional): Updated topic or subject of the note. confirm (bool, optional):
- False → Preview only (default, no persistence) - True → Update and permanently save the note

Returns: Dict with success status and note data: - success (bool): Whether the request was successful - message (str, optional): Success or error message - noteId (str, optional): Updated note ID - error (str, optional): Error message if request failed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
controlIdYes
noteIdYes
assessmentIdYes
notesYes
topicYes
confirmNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, description carries full burden effectively—discloses preview mode, persistence behavior, and markdown format requirements; no contradictions.

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?

Well-structured with purposeful headers (PURPOSE, CONFIRMATION-BASED SAFETY FLOW) and front-loaded intent; emoji formatting slightly verbose but doesn't obscure meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequately covers the confirmation complexity and explains return values despite output schema existing; could explicitly reference create_control_note sibling for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Comprehensive compensation for 0% schema description coverage—details all 6 parameters including format constraints (markdown), entity relationships, and confirmation semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb+resource ('updates an existing documentation note'), implicitly distinguishes from create_control_note via 'existing'/'previously created' language but lacks explicit sibling contrast.

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?

Excellent confirmation-flow guidance (preview vs permanent save) provides clear behavioral context, though lacks explicit 'when not to use' or alternative tool references.

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/ComplianceCow/cow-mcp'

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