Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

create_control_note

Create markdown documentation notes attached to compliance controls, with preview and confirmation to prevent unintended changes.

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

Behavior4/5

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

Without annotations, the description fully discloses the dual behavior: preview mode vs. permanent creation. It explains the return values and that the note is attached to a control. It does not mention permissions or side effects, but the core behavioral split is well-covered.

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 detailed but well-organized with sections, bullet points, and formatting. Each part serves a purpose, though it is slightly longer than necessary. The main purpose is front-loaded.

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 tool's complexity (confirmation flow, five parameters, detailed return schema), the description is complete. It explains the preview behavior, the creation mode, and the full return object, making it self-sufficient even without annotations.

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?

The input schema has 0% description coverage, but the description lists all five parameters with their purposes, required status, and the confirm parameter's boolean options. It also explains the return structure, adding significant value 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 creates a documentation note attached to a control, specifying the verb 'create' and the resource 'control note'. It distinguishes itself from siblings like 'update_control_note' and 'list_control_notes' by focusing on creation.

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?

Provides explicit guidance on the confirmation-based safety flow with confirm=False for preview and confirm=True for persistence. While it does not explicitly mention when to use this tool versus alternatives, the flow is clearly explained.

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