Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

create_control_note

Create and attach markdown documentation notes to compliance controls with preview mode before permanent confirmation.

Instructions

Create a documentation note on a control.

This tool creates a markdown documentation note that is attached to a control.

✅ CONFIRMATION-BASED SAFETY FLOW

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

  • When confirm=True: → The note is permanently created and attached to the control.

Args: controlId (str): The control ID where the note will be attached (required). assessmentId (str): The assessment ID or asset ID that contains the control (required). notes (str): The documentation content in MARKDOWN format (required). topic (str, optional): Topic or subject of the note. confirm (bool, optional):
- False → Preview only (default, no persistence) - True → Create and permanently attach the note

Returns: Dict with success status and note data: - success (bool): Whether the request was successful - note (dict, optional): Created note object containing: - id (str): Note ID - topic (str): Note topic - notes (str): Note content in markdown format - controlId (str): Control ID the note is attached to - assessmentId (str): Assessment ID - error (str, optional): Error message if request failed - next_action (str, optional): Recommended next action

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
controlIdYes
assessmentIdYes
notesYes
topicYes
confirmNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses critical safety flow (preview mode doesn't persist), markdown format requirement, and permanent attachment behavior—essential context given no annotations provided.

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 clear sections and front-loaded purpose; slightly redundant in documenting return values since output schema exists, but every section provides actionable guidance.

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?

Comprehensive coverage given zero schema descriptions; explains markdown requirement, confirmation workflow, and all parameter meanings, fully preparing the agent for invocation.

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?

Compensates fully for 0% schema description coverage by providing detailed semantics for all 5 parameters, including format constraints (markdown) and boolean behavior (confirm flag).

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?

Opens with specific verb (Create) + resource (documentation note/control), and distinguishes from sibling 'update_control_config_note' via explicit creation semantics.

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 explanation of confirmation flow (when to use confirm=True vs False for preview vs persistence), though lacks explicit comparison to 'update' sibling for create-vs-update decisions.

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